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
A PR bundles a modernization pass on a working module, a new abstraction, and telemetry wiring all in the same change. The author argues that it will "set the team up for the future," but the reviewers are not sure the proposal is worth the churn.
Write a review memo that gives the safest recommendation and a clearer alternative.
Write decision.md with your review and safer alternative.