sporkwace/guv
enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. use when the user asks whether to refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift. do not use as the primary implementation skill for routine debugging, bug fixes, feature coding, or language-specific coding unless a no-op, minimal-diff, or architecture-conflict judgment is needed.
98
100%
Does it follow best practices?
Impact
96%
1.33xAverage score across 5 eval scenarios
Passed
No known issues
task.mdevals/scenario-2/
Receipt Formatter Change
Problem / Feature Description
A teammate thinks the receipt formatter should be extracted into a shared helper before a tiny behavior tweak lands in the billing flow. They are worried that the current approach is starting to drift, but they do not want a broad rewrite if a smaller change would keep the codebase stable.
The team wants a governance review that says whether the change should proceed and, if so, what the narrowest safe path would look like.
Output Specification
Write decision.md with your review and the smallest safe change plan if a change is justified.