Content
77%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 body is a tight, highly actionable gate pipeline: every step has a concrete command, explicit stop conditions, validation checkpoints, and recovery loops, with no filler or concept padding. Its weaknesses are token-level duplication between the inline gates, the Red flags table, and the Error handling section, plus a 310-line monolith whose red-flag/error tables belong in a references/ bundle file, and one PowerShell-only snippet in an otherwise bash-based skill.
Suggestions
Move the Red flags table and the Error handling bullets into a references/red-flags.md file and keep a one-line pointer in SKILL.md — they restate gate rules already stated inline and account for much of the 310-line length.
Provide the Gate 1 run-id/worktree block in bash (or both shells) so it is copy-paste executable on the same environments as the Gate 0 bash snippet; only the guid-minting differs between shells.
Deduplicate the three restatements of merge-conflict handling (Update from main section, Red flags row, Error handling bullet) into a single canonical location with the other two pointing to it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean, imperative style throughout with zero concept explanations ('A bug-fix PR is guilty and untrusted. Default action is stop.'), but the 33-row Red flags table and 17-bullet Error handling section substantially restate rules already given inline (e.g., merge-conflict handling and worktree-path collisions each appear three times). Fits anchor 4 (efficient, minor trimming possible) more than 3, since there is no padding or explanation of things Claude already knows — only deliberate but token-costly repetition. | 4 / 5 |
Actionability | Provides concrete, executable commands for nearly every step — 'gh pr view <N> --json title,body,author,files,commits,url', 'git worktree add --detach $mainWt $mainSha', 'gh api --paginate "repos/<owner>/<repo>/pulls/<N>/comments"'. Falls short of anchor 5 because the Gate 1 run-id block is PowerShell-only while Gate 0 uses bash, so that block is not copy-paste ready on non-Windows shells — a minor gap consistent with anchor 4. | 4 / 5 |
Workflow Clarity | Clear, explicit sequence (Gate 0 → update from main → Gate 1 → Gate 2 → CodeRabbit check → report and wait) with HARD-GATE validation checkpoints, feedback loops for error recovery (repro must fail on main and pass on the PR; conflicts are resolved, committed, pushed, then Gate 1 restarts; worktree collisions mint a new run id), and a dedicated Error handling section enumerating failure modes. This matches the anchor-5 pattern of explicit validation steps with retry/stop paths for a destructive, merge-and-push workflow. | 5 / 5 |
Progressive Disclosure | The 310-line body is a single well-sectioned file with no bundle files; the security checklist is appropriately externalized (loaded from pinned origin/main via 'git show'), but the Red flags table and Error handling detail are inline candidates for a references/ file. Anchor 3 fits — structure exists and content is organized, but material that should be in separate files (the ~60 lines of red-flag/error tables) is inlined in SKILL.md. Not 4: the bulk gate procedures are not split out and navigation relies on one long document; not 2: sections are clearly headed and one external reference is properly signaled. | 3 / 5 |
Total | 16 / 20 Passed |