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 procedural content: terse, fully executable, and sequenced with real validation checkpoints and a safety gate on destructive cleanup. The only minor gap is reference hygiene — overlapping external links with fragile relative paths.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 15-line body is lean and imperative throughout — "Require an explicit `<pr>`", "Fetch `origin/main`, inspect `git rev-list --parents -n 1`" — with no explanation of concepts Claude already knows; every token earns its place. | 5 / 5 |
Actionability | Fully executable guidance with copy-paste-ready commands and placeholders, covering both the two-parent merge case (`git merge-base --is-ancestor`, `git show --remerge-diff`) and the squash case (`git diff --stat`, `git patch-id --stable`), plus the `gh pr view` verification call. | 5 / 5 |
Workflow Clarity | A clear 5-step sequence with an explicit validation checkpoint (verify `state` is `MERGED` with non-null `mergeCommit` and `mergedAt`), error recovery (fix-forward with a new PR if work was missed), and destructive operations gated on an explicit cleanup request. | 5 / 5 |
Progressive Disclosure | The short body is well organized with clearly signaled one-level references to the workflow docs and detailed procedure, but the two overlapping external references use fragile `../../../` paths that escape the skill directory, and one points at another copy of SKILL.md, creating mild ambiguity about where authoritative detail lives. | 4 / 5 |
Total | 19 / 20 Passed |