Content
87%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 concise and highly actionable with executable commands and tidy structure. Its main weakness is the absence of validation/confirmation steps around a destructive branch-deletion workflow.
Suggestions
Add a verification checkpoint before deletion, e.g. confirm the branch is actually merged into main ('git branch --merged main') before running 'git branch -D'.
Include an explicit confirmation or guard for the remote deletion step ('git push origin --delete'), since it is destructive and hard to reverse.
Note handling for the case where pulling main fails or the branch is the current branch, to make the workflow robust against error states.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no padding or re-explanation of git concepts Claude already knows; every section (Workflow, Commands, Important Notes) earns its place. | 5 / 5 |
Actionability | Provides a fully executable, copy-paste-ready command chain covering the common case, with the '<branch-name>' placeholder the only required substitution. | 5 / 5 |
Workflow Clarity | A clear sequence with concrete commands is present, but this is a destructive operation (local and remote branch deletion with force-delete) that lacks any validation or confirmation checkpoint, which caps the score per the rubric guideline. | 3 / 5 |
Progressive Disclosure | A simple skill under 50 lines with no external references; it is well-organized into clearly labeled sections, meeting the simple-skill exception for a top score. | 5 / 5 |
Total | 18 / 20 Passed |