Content
88%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 skill content: exact commands, named scripts, explicit validation checkpoints, and error-recovery guidance make it directly executable. The only real weaknesses are mild verbosity in the step-1 caution detail and dated incident references inlined in the main flow rather than separated out.
Suggestions
Move the 'Restarting a branch whose PR already merged' anecdote (with its 2026-08-14 date and PR #1944 reference) into a short 'Known pitfalls' or reference section so dated incident details don't sit in the main workflow.
Tighten step 1 by consolidating the three repeated snapshot/compare instructions into one 'record → re-check → compare → stop on any drift' pattern stated once.
Consider splitting the detailed preconditions for shared worktrees into a referenced file (e.g. references/shared-worktree-safety.md) to keep the main sequence lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with repo-specific operational detail and assumes git competence — no space is spent explaining concepts Claude already knows. Minor trimming is possible (step 1 repeats the snapshot-compare instructions), and dated incident references ('Observed 2026-08-14', 'PR #1782', 'PR #1944') are time-sensitive details not placed in an old-patterns section, keeping it below the lean-everywhere anchor. | 4 / 5 |
Actionability | Fully executable guidance throughout: exact commands ('git status --porcelain=v1 -z --untracked-files=all', 'npm run verify:pr-local', 'gh pr create --base main', 'npm run pr:areas'), named scripts with paths ('node scripts/check-base-freshness.mjs', 'scripts/guard-push.mjs'), and all five guard override env variables listed. Copy-paste ready and covering the common cases. | 5 / 5 |
Workflow Clarity | A clear 9-step sequence with explicit validation checkpoints (record/compare the cached index before staging, verify the commit with 'git show --name-only --format=fuller HEAD', confirm the remote tip with 'git ls-remote', 'Paste the decisive proof line') and error-recovery loops (stale ref after merge → 'git remote prune origin' then push; heed guard blocks rather than overriding). This matches the top anchor including feedback loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so all content is in SKILL.md; sections are well organized (Preconditions, numbered Steps, Requires explicit confirmation) and repo-doc links are clearly signaled with anchors. However, the ~100-line body inlines material that could sit in a reference file — the merged-branch restart anecdote and the long step-1 caution block — so structure is good but not cleanly split, and the under-50-line simple-skill exception does not apply. | 4 / 5 |
Total | 18 / 20 Passed |