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
architecture-review-checklist.mdreferences/
Architecture Review Checklist
Before endorsing an architectural or scope-widening change, check whether it:
- adds or changes a source of truth
- adds a new write path
- bypasses an established runtime boundary
- duplicates an existing surface or capability
- changes sync directionality or ownership
- weakens audit history or traceability
- relies on fuzzy matching where exact identity is required
- creates a second way to perform the same operation
- conflicts with a phase gate, ADR, or non-negotiable constraint
- lacks an acceptance test for the claimed benefit
If any answer is yes, surface the conflict before implementation.