Content
78%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.
An exemplary lean, well-sequenced workflow with a genuine validation-and-fix loop — the main weakness is the near-total absence of executable git commands, which leaves the agent to reconstruct them from memory. The closing steps are also underspecified relative to the rest.
Suggestions
Inline the key commands per step: `git status` / `git log --merge --patch` for inspection, `git add` + `git commit` to finish a merge, `git rebase --continue` for rebases.
Add a pre-finish validation check that no conflict markers (`<<<<<<<`) remain in staged files before committing.
Make the finish step concrete about rebases: repeat `git rebase --continue` until all commits are rebased rather than describing it abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Fourteen lean lines with zero padding; phrases like "Understand deeply why each change was made" and "Do **not** invent new behaviour" assume Claude's competence and only state what it wouldn't already know. Every token earns its place — matches the anchor-5 example. | 5 / 5 |
Actionability | Steps are directionally concrete ("Check git history", "run them, typically typecheck, then tests, then format") but contain no executable commands — no `git status`, `git log --merge`, `git add`, or `git rebase --continue`. This matches anchor 3 ('concrete guidance but incomplete; missing key details') rather than 4, which requires concrete code or commands. | 3 / 5 |
Workflow Clarity | A clear 5-step sequence with an explicit validation checkpoint (step 4: run automated checks and "Fix anything the merge broke" — a fix-and-retry feedback loop). Not 5: there is no check for leftover conflict markers before committing, and "continue the rebase process" is stated abstractly without the command. | 4 / 5 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no bundle files and no content that belongs in separate reference files; the numbered, bold-headed sections are well-organized and easy to navigate, so the simple-skill provision applies. | 5 / 5 |
Total | 17 / 20 Passed |