Content
96%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.
Highly operational, lean content that assumes Claude's git competence while adding real procedural value: exact commands, verification checkpoints, recovery paths, and safety checklists for destructive operations. The only structural improvement is moving the peripheral PR-attachment upload protocol into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is operational directives with concrete commands and zero explanation of concepts Claude already knows (it never explains what rebase or reflog are). Lines like "Be exact, conservative, and evidence-led" set tone in a single sentence — every token earns its place. | 5 / 5 |
Actionability | Copy-paste-ready guidance throughout: the parallel Ground Truth command block, "GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash <base>", "use --force-with-lease, never plain --force", "git blame -L start,end -- file", and exact HTTP endpoints with parameters for the attachment flow. Commands cover the common cases for each mode. | 5 / 5 |
Workflow Clarity | The Mode Gate classifies requests first, Commit Mode is a numbered sequence with pre/post checkpoints ("Before each commit, verify git diff --staged --stat"), and Safety Checks is an explicit pre-write checklist with recovery paths ("use git rebase --abort first"). Validation for the destructive history-rewriting operations is explicit, so the destructive-operation cap at 3 does not apply. | 5 / 5 |
Progressive Disclosure | Well-organized, self-contained sections with clear headers and no nested references (no bundle files exist), which is good structure. Not 5 because the skill exceeds 50 lines and the PR Body Evidence Attachments section — a GitHub upload protocol peripheral to core git operations — is a natural candidate for a one-level-deep reference file. | 4 / 5 |
Total | 19 / 20 Passed |