Content
86%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 well-structured reference skill: executable commands throughout, a real one-level-deep reference file for worked examples, and safety guidance for the destructive operations it covers. The main gap is that validation steps for risky sequences (rebase, force-push) are stated as best-practice bullets rather than inline checkpoints within the workflows themselves.
Suggestions
Embed validation as an explicit step in the interactive-rebase and force-push sequences (e.g., run tests after rebase, then `git push --force-with-lease`), rather than only as a best-practices bullet.
Trim decorative phrases like "the Swiss Army knife of Git history editing" and "Future you will thank present you".
Add a brief inline conflict-resolution loop (`git status` → fix → `git add` → `git rebase --continue`) to the interactive rebase section instead of deferring it entirely to references/details.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by lean, commented command blocks that assume Git competence, with only minor trimmable flavor ("the Swiss Army knife of Git history editing", "Future you will thank present you") — efficient with small instances of over-explanation, matching the level-4 anchor rather than the fully lean level-5 anchor or the noticeably padded level-3 one. | 4 / 5 |
Actionability | Every technique ships copy-paste-ready, executable commands with per-line comments (rebase, cherry-pick, bisect including `git bisect run ./test.sh`, worktree, reflog recovery), covering the common cases comprehensively. | 5 / 5 |
Workflow Clarity | Sequences are clear (the bisect loop is an explicit test-and-mark feedback loop) and destructive operations do carry validation/safety checkpoints — "Test Before Force Push", backup-branch-then-reset recovery, and the stash-first warning before `reset --hard`. It stays at 4 rather than 5 because validation is presented as best-practice bullets rather than embedded checkpoints inside the rebase and force-push sequences themselves, and conflict-resolution steps live only in the reference file. | 4 / 5 |
Progressive Disclosure | SKILL.md is a well-sectioned overview with a single clearly signaled, one-level-deep reference ("Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient") that is a real file containing the worked examples, matching the top anchor; scoring against the actual bundle confirms no nesting beyond one level. | 5 / 5 |
Total | 18 / 20 Passed |