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
1.33x
Quality
100%
Does it follow best practices?
Impact
96%
1.33xAverage score across 5 eval scenarios
Securityby
Passed
No known issues
minimal-diff-rules.mdreferences/
Minimal-Diff Rules
Prefer the smallest safe diff that satisfies the real objective.
Do:
- touch only relevant files
- preserve existing behavior unless change is required
- add focused tests for changed behavior
- use existing abstractions and conventions
- explain why each changed area is necessary
Do not:
- rewrite working code for aesthetics
- introduce abstractions before duplication is proven
- mix refactor and behavior change without saying so
- widen task scope silently
- rename or reorganize broadly unless that is the task