I built an action that solves a problem we kept running into — developers modifying critical code without knowing why it was implemented a certain way.
How it works:
- You write decision records in markdown (what was decided, why, which files are affected)
- When a PR touches those files, the action automatically posts a comment with the relevant context
- Comments are idempotent (updates instead of spamming), supports glob patterns, regex content matching, and handles PRs with 3000+ files
What it's NOT:
- Not a linter or code quality tool
- No external network calls — runs entirely in your runner
- No data leaves GitHub
MIT licensed, fully open source
It's basically CODEOWNERS but for "why" instead of "who."
I built an action that solves a problem we kept running into — developers modifying critical code without knowing why it was implemented a certain way.
How it works:
What it's NOT:
MIT licensed, fully open source
It's basically CODEOWNERS but for "why" instead of "who."
Repo: Decision guardian