Content
96%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.
Excellent operational content: fully executable gh/git commands, explicit validation checkpoints and recovery loops around a merge (irreversible) operation, and tight, padding-free prose. The only structural note is that at ~96 lines with moderately detailed sub-procedures (issue search, changeset handling) inlined in a single file, it is at the upper bound of what belongs directly in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, imperative, and assumes competence: no concept explanations, no padding, just concrete commands, conditions, and decision rules. Every line is instruction; the only repetition (head-SHA pinning restated at merge time and in 'Do Not') reads as deliberate safety emphasis for a destructive operation rather than filler. Not the level below (4) because there is no over-explanation to trim. | 5 / 5 |
Actionability | Every step carries a copy-paste-ready gh/git command with concrete flags (--match-head-commit, --squash, --json fields), and edge branches give exact fallback behavior (manual merge command, comment-vs-close decision rule). This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | The 8-step sequence is explicitly ordered with validation checkpoints throughout: readiness gating on pinned head SHA, check-state verification, HEAD comparison before branch review, re-reading the pin before merge, and post-merge state confirmation. Error-recovery feedback loops are present (pending/failing checks -> do not merge; ambiguous issue -> comment and ask instead of closing; missing changeset -> follow-up PR), matching the top anchor. | 5 / 5 |
Progressive Disclosure | A single-file skill with clean section structure (Workflow / Do Not) and no nested references; the repo files it names (AGENTS.md, scripts/pr-merge) are environment targets, not bundle references. It is well above anchor 3 (structure is clear, nothing is buried), but the body runs ~96 lines — over the under-50-lines simple-skill exception — and detailed inline material like the step-5 issue-search heuristics could live in a one-level-deep reference, so it does not fully meet anchor 5's 'content appropriately split'. | 4 / 5 |
Total | 19 / 20 Passed |