gormes-review-scorecard

A local code review scorecard quantifies production-readiness by applying structured scoring deductions for missing evidence, bugs, or documentation drift. It generates a 1–5 readiness score and required actions, serving as a conservative quality gate when external review tools are inaccessible.

A local quality gate evaluates uncommitted Go changes using a structured scorecard that deducts points for missing required evidence and safety concerns. It outputs a 1–5 readiness score to indicate whether a change warrants further external review before release.

Run the scorecard against your uncommitted changes or PR to obtain a 1–5 readiness score and required actions. This preflight check identifies potential UX, scope, or safety concerns before routing the change to a Greptile loop or release workflow.

Yes, the scorecard applies specifically to changes with green tests but potential UX, scope, or safety concerns. It satisfies requirements for required evidence checks and structured scoring deductions, ensuring production-readiness is verified beyond just passing tests.

Use a local review scorecard when external review tooling is unavailable, as a preflight check before a release, or when a change has green tests but potential safety concerns. It provides a conservative quality gate to determine if changes warrant external review routing.

No, the scorecard runs locally as a standalone quality gate without external dependencies. It quantifies production-readiness by applying structured scoring deductions and required evidence checks directly to your uncommitted changes or PR.