Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-sequenced, highly actionable procedure with explicit validation checkpoints and genuine review feedback loops, and it stays lean by assuming competence. Its main weaknesses are minor redundancy (the duplicated ALL-CAPS Greptile instruction and the 'Hard rules' section) and a couple of places where concrete commands are left implicit.
Suggestions
Delete the ALL-CAPS 'RUN GREPTILE UNTIL IT GETS TO 5/5 - DO NOT STOP UNTIL...' paragraph — it duplicates the first bullet of section 5 — and instead emphasize the termination criteria once, e.g. 'Stop only when Greptile is 5/5, all tests and verification checks pass, and there are no merge conflicts.'
Consolidate the 'Hard rules' section into the steps where each rule already appears (sections 1 and 4) rather than repeating them, keeping a single source of truth.
Make the remaining vague steps concrete: give the exact rebase command form (e.g. 'git fetch <remote> && git rebase <remote>/master') and a minimal 'gh pr create' invocation with the --title/--body template shape.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes competence — imperative bullets, exact commit trailer, numeric thresholds — with no re-teaching of known concepts. It falls short of lean/5 because of redundancy: the ALL-CAPS 'RUN GREPTILE UNTIL IT GETS TO 5/5 - DO NOT STOP...' restates the preceding bullet, and the 'Hard rules' section duplicates rules already given in sections 1 ('no orphaned stashes... no dropped files') and 4 ('Record the PR URL immediately'). | 4 / 5 |
Actionability | Concrete, mostly executable guidance throughout: 'git rev-parse --git-dir', 'git branch --show-current', 'gh', the exact trailer 'Co-Authored-By: Paperclip <noreply@paperclip.ing>', the 'under 100 changed files' limit, 'max 20 turns', and the CONTRIBUTING.md URL. Minor gaps keep it below 5: no copy-paste 'gh pr create' form, and 'rebase (or otherwise replay) your branch' leaves the mechanism open rather than giving an exact command. | 4 / 5 |
Workflow Clarity | A clearly numbered 0–6 sequence with explicit validation checkpoints (worktree verification, post-rebase re-verification 'build/tests... still pass', the guardrails checklist) and true feedback loops with defined termination criteria — 'repeat until Greptile gives 5/5 with zero unresolved comments (max 20 turns). Do not stop early' — plus renumber/re-run recovery for migration conflicts. This matches the anchor 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'. | 5 / 5 |
Progressive Disclosure | The body is a well-sectioned procedure with one-level-deep pointers only (CONTRIBUTING.md URL, /greploop and /prcheckloop skills) and no bundle files to organize, which is appropriate for a ~80-line procedural skill. It misses 5 due to minor organization gaps — the redundant 'Hard rules' section re-states earlier rules instead of consolidating them, slightly muddying navigation. | 4 / 5 |
Total | 17 / 20 Passed |