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-engineered, safety-conscious workflow: nearly every step is executable bash, validation boundaries are explicit, and edge cases (diverged source, absent remote branch, empty diff) are handled deliberately. The main gaps are a couple of policy-only steps lacking concrete commands and some prose that repeats what the code already conveys.
Suggestions
Add concrete commands to step 4's cleanup (e.g., how to check PR merge state via gh pr view/list and the exact git branch -d / git push --delete invocations) so that common-case step is as executable as the rest.
Trim the prose in step 5 that restates the case-statement logic (the status-code outcomes are already self-documenting in the code block), keeping only the intent sentence and the ask-on-divergence rule.
Break the single ## Workflow section into a few sub-sections (Detect, Clean up, Branch, PR) or otherwise signal the phases so the ~112-line procedure is easier to navigate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and almost entirely executable bash with no padding of concepts Claude already knows, but step 5's prose ("Treat the lookup status as a safety boundary…") duplicates the logic already expressed in the case statement, and the opening line restates the description. These are minor over-explanations that could be trimmed, so it sits at 4 rather than the every-token-earns-its-place level. | 4 / 5 |
Actionability | Most steps (detection, fetch/prune, remote lookup, checkout variants, push, PR creation) are copy-paste-ready with proper quoting, but step 4's branch cleanup — a common case in this workflow — and step 3's dirty-tree check give policy guidance without the specific commands (e.g., gh pr view, git branch -d). This matches "mostly executable guidance with minor gaps" rather than full coverage of common cases. | 4 / 5 |
Workflow Clarity | Eight clearly sequenced steps with explicit validation checkpoints (dirty-tree check, ls-remote exit-code boundary with per-status handling, --ff-only with ask-on-divergence, empty-commit guard, PR-existence check) and error-recovery guidance (report and stop on lookup failure; ask rather than auto-merge). This matches the top anchor, and the destructive-operation cap does not apply because validation is thoroughly present. | 5 / 5 |
Progressive Disclosure | A single cohesive ~112-line file with one ## Workflow section and no bundle files; the content appropriately lives in one file for a unified procedure, but it exceeds the under-50-line simple-skill threshold and has minimal sectioning (no sub-headers separating detection, cleanup, branching, and PR phases). Good structure with minor organization gaps puts it at 4. | 4 / 5 |
Total | 17 / 20 Passed |