Menu
Use when checking a Gormes pull request for unresolved comments, failing checks, incomplete description, missing validation evidence, or merge readiness before Greptile/release review.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-pr-check |
| description | Use when checking a Gormes pull request for unresolved comments, failing checks, incomplete description, missing validation evidence, or merge readiness before Greptile/release review. |
Adapted from github.com/greptileai/skills check-pr for Gormes' development-only workflow.
Use this before gormes-greptile-loop, before asking for human review, or when the user asks whether a PR is ready.
git rev-parse --show-toplevel).development; do not create/switch feature branches.gh if PR metadata is needed.Identify target PR
gh pr view --json number,url,title,headRefName,headRefOid.Collect evidence
git status --short --branch.Classify issues
| Category | Meaning | Next skill |
|---|---|---|
| Failing check | CI or required local gate failed | gormes-review-loop or gormes-tdd-slice |
| Review feedback | Human/Greptile comment needs action | gormes-greptile-loop or gormes-review-loop |
| Missing evidence | PR lacks test/validation notes | update PR body or final report |
| Scope drift | PR mixes unrelated concerns | ask user or split commits if still local |
| Informational | no action required | record only |
Do not fix unless requested
gormes-review-loop or gormes-greptile-loop.Optional PR body update
PR readiness check
PR: <url>
Branch: development
Checks: <passing/pending/failing>
Reviews: <approved/changes/unresolved>
Description: <complete/incomplete>
Local status: <clean/dirty>
Actionable items:
1. <item> — <next skill/command>
Ready to merge: <yes/no>
For docs/skills-only PR checks:
go test ./internal/skills -count=1go run ./cmd/progress validategit diff --checkFor runtime PR checks, require the full gate before readiness:
go test ./... -count=1go run ./cmd/progress validategit diff --check