Content
81%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 body is highly actionable with strong validation gates and feedback loops for a risky shipping workflow, though it leans verbose in its explanatory prose and keeps all material in one long file.
Suggestions
Tighten the explanatory prose in step 2 and the Phase A/B rationale to concrete imperatives, trimming the 'why this can go wrong' narratives.
Consider moving the PR Description Format template and Commit Message Format into a reference file linked one level deep to reduce SKILL.md length.
Collapse the repeated 'do not ship / exit 1' rationale comments in the bash blocks to a single shared note.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and repo-specific, but step 2 and the Phase A/B prose carry lengthy explanations of why drift happens that could be tightened without losing the actionable guidance. | 3 / 5 |
Actionability | Provides copy-paste-ready bash blocks, exact git and gh commands, and explicit per-job exit-code gating that covers the common shipping cases fully. | 5 / 5 |
Workflow Clarity | A destructive/batch workflow with explicit validation checkpoints (sync check, post-rebase re-verify, Phase A status gating, Phase B lint+audit gating, final commit-content comparison) and feedback loops for error recovery. | 5 / 5 |
Progressive Disclosure | Single well-sectioned file with clear navigation and no nested references, but at 159 lines it inlines the PR/commit templates that could be split out, leaving minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |