Content
92%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.
A strong, highly operational skill body: a 9-step workflow with concrete git/gh commands, explicit validation checkpoints, error-recovery handling for stash conflicts and cleanup failures, and mode selection (reuse vs. create temporary worktree) resolved before any state is moved. The only improvement space is minor textual redundancy — the original-checkout/cleanup-cwd rule and the stop-and-ask clauses are each stated more than once, and Guardrails partially duplicates the steps.
Suggestions
State the cleanup-cwd rule once (in step 8) and have step 2 only say 'record the original checkout path' without re-explaining its use.
Consolidate the repeated 'stop and ask before doing something misleading' guidance into a single Guardrails bullet instead of restating it in steps 2, 3, and 5.
Trim Guardrails bullets that restate in-step constraints (e.g. never removing a dirty worktree already appears in step 8) so each safety rule lives in one place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — it never explains what a worktree, stash, or Conventional Commit is — and nearly every bullet is an instruction. But there are minor trims available: the cleanup cwd rule is stated in step 2 ('Record the original checkout path up front... use that original checkout... in step 8') and again in step 8, 'stop and ask/clarify' appears in steps 2, 3, and 5, and the Guardrails section restates constraints already inlined in steps 3, 5, and 8. That matches the score-4 anchor (efficient, minor over-explanation that could be trimmed) rather than score 5's 'every token earns its place'. | 4 / 5 |
Actionability | Concrete, copy-ready commands appear at every decision point: `git stash push --include-untracked -m "worktree-pr:<branch>:<timestamp>"`, `git worktree add -b <branch> ../.worktrees/<repo>/<branch> HEAD`, `git push -u origin <branch>` with `--force-with-lease` guidance, and `gh pr create --base <base> --head <branch> --title <title> --body <body>`. Even the temporary-worktree path is a deterministic template rather than an ad hoc guess. This is the score-5 anchor — fully executable guidance covering the common cases; score 4 would require missing key details, and none are. | 5 / 5 |
Workflow Clarity | Nine explicitly sequenced steps with validation checkpoints throughout: capture repo state before moving anything (step 2), verify the stash landed in the new worktree (step 3), re-run `git status --short --branch` and run formatter/typecheck/tests in the execution worktree (step 4), confirm clean status after commit (step 5), check `gh auth status` before planning (step 2), and error-recovery loops for stash conflicts and the cwd-stuck-cleanup retry (step 8). Because this is a destructive/batch-adjacent operation, the cap of 3 would apply only if validation were missing — it is not; feedback loops are explicit, matching the score-5 anchor. | 5 / 5 |
Progressive Disclosure | The single external reference is real, relevant, one level deep, and well signaled: 'PR title and commit message must follow [PR and Commit Conventions](references/pr-conventions.md)' (references/pr-conventions.md exists, 17 lines, and contains exactly the convention details kept out of SKILL.md). The workflow itself — which must be inline to be followed — stays in the body under clear section headers (Workflow, Guardrails). This matches the score-5 anchor: appropriate split, well-signaled one-level references, easy navigation. | 5 / 5 |
Total | 19 / 20 Passed |