Content
90%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, command-first skill body: copy-paste-ready git/gh blocks, numbered workflows with verify steps and abort paths, and no padding. The gaps are the missing explicit review checkpoint before the batch branch deletion and five self-contained topics that could be split into reference files for progressive disclosure.
Suggestions
Insert an explicit checkpoint between listing and deleting merged branches (e.g., 'Review the list — these branches will be deleted' before the xargs step) to close the validation gap in the batch-delete workflow.
Move peripheral sections (monorepo tags, .gitignore-first init, license audit) into a one-level-deep references/ file, keeping SKILL.md as a concise overview of the core PR/conflict workflows.
Add the promised squash-and-merge section or remove the claim from the description so the body's coverage matches the advertised scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is almost entirely executable commands with one-line framing — no git basics are re-explained and every section earns its tokens. The single intro sentence ('Guided workflows for common git operations that benefit from structured steps') is the only near-filler, which is insufficient to drop from the lean/efficient anchor. | 5 / 5 |
Actionability | Nearly every step is a copy-paste-ready git/gh command block, including a complete `gh pr create` heredoc, safe grep exclusion filters for branch deletion, and a concrete monorepo tag pattern. Steps that are judgment-based (conflict-resolution policy) are inherently non-automatable and stated as concrete rules. | 5 / 5 |
Workflow Clarity | PR preparation and conflict resolution are clearly numbered with explicit **Verify** steps and abort/recovery paths. Branch cleanup is a batch-destructive operation that lists merged branches before deleting and uses safe `-d`, but it lacks an explicit checkpoint instructing the reader to review the listed branches before the xargs delete — a minor validation gap placing it at the 'most checkpoints present' anchor rather than 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the content is self-contained with clear section headers, which is good structure. However, the doc runs ~140 lines across five distinct topics (PR prep, cleanup, conflicts, tags, init/license audits), exceeding the under-50-line simple-skill exception, and several peripheral sections (monorepo tags, .gitignore init, license audit) could live in one-level-deep references — the 'most content appropriately placed, minor organization gaps' anchor. | 4 / 5 |
Total | 18 / 20 Passed |