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
As Abraham Lincoln famously said,
Coding LLMs are generally over-compliant. They optimize for “do the requested transformation” rather than “protect the codebase from unnecessary change.”
Enter, the Guv. Guv is a skill that enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. Plays well with Superpowers.