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-1/
Should we touch the formatter?
Problem / Feature Description
The release manager asked whether a small invoice-reference formatter should be "cleaned up" before the next release freeze. The helper already passes its tests, and nobody has reported a concrete defect, but the code looks a little more verbose than the team would like.
The team wants a short governance review before anyone spends time on it.
Output Specification
Write decision.md with a concise governance review and recommendation.