Menu
Use when Greptile is unavailable or before requesting external review to assign a conservative 1-5 production-readiness score to a Gormes change from source evidence and validation results.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.
Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.
Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.
Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.
Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.
Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.
| name | gormes-review-scorecard |
| description | Use when Greptile is unavailable or before requesting external review to assign a conservative 1-5 production-readiness score to a Gormes change from source evidence and validation results. |
This is a local, conservative version of the Greptile-style 5/5 quality gate. It does not replace Greptile or CI; it tells the agent whether the work deserves external review yet.
gormes-greptile-loop or gormes-release.Start at 5. Subtract for evidence-backed problems:
| Deduction | Problem |
|---|---|
| -2 | failing required test/check, known runtime bug, data-loss/security risk |
| -1 | missing focused test for changed behavior |
| -1 | unclear user-visible contract or parity evidence |
| -1 | mixed concerns that should be split |
| -1 | weak validation notes or unverified manual claim |
| -1 | docs/progress/skill routing drift |
Minimum score is 1. Never award 5/5 with dirty uncommitted production code unless the review scope is explicitly local/uncommitted.
git status --short --branchgit diff --stat or git show --stat for committed work.go test ./internal/skills -count=1, go run ./cmd/progress validate, git diff --checkgo test ./... -count=1, go run ./cmd/progress validate, git diff --checkgormes-tdd-slicegormes-review-loop or gormes-greptile-loopgormes-progress-slicergormes-architecture-zoomoutGormes review scorecard
Scope: <diff/commit/PR>
Score: <n>/5
Evidence: <commands/files>
Deductions:
- <points>: <reason + exact evidence>
Required to reach 5/5:
1. <smallest next action + skill>