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
no-op-policy.mdreferences/
No-Op Policy
A correct no-op is better than an unnecessary diff.
Recommend no change when code is already correct, readable, tested, convention-aligned, and proportionate to the problem.
Require a diff only when it improves at least one of:
- correctness
- security
- performance
- type safety
- maintainability
- test coverage
- observability
- domain clarity
- removal of proven duplication
Reject changes justified only by preference, novelty, style, or speculative future needs.