Content
87%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, highly actionable workflow with executable commands and a well-structured single-level reference. The main gap is workflow clarity: validation is present but only at the end rather than as interleaved checkpoints with explicit error-recovery loops for these destructive merge operations.
Suggestions
Add explicit validation checkpoints inside the merge workflow (e.g., after conflict resolution: run lint/tests before committing, and a retry loop if they fail) rather than only verifying at the end.
In the conflicting-PR step, include a validate→fix→retry loop (resolve → `git status`/build check → re-resolve if still failing) to make the error-recovery path explicit.
Clarify in step 6 what to do when ruff/pytest fail after a merge (revert vs. fix-forward), turning the terminal verification into a real feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — executable gh/git commands with no "what is a PR" tutorial or library background — and every section (principles, workflow, checklist, pitfalls) earns its tokens, matching the lean-and-efficient anchor. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands with placeholders throughout — `gh pr merge --squash`, `git fetch origin pull/NUMBER/head`, `git apply --exclude=...`, `git commit --author=...`, `ruff check`, `pytest` — matching the executable-and-specific anchor. | 3 / 3 |
Workflow Clarity | A clear numbered 1–6 sequence exists and a terminal Post-Merge Verification block plus an Attribution Checklist, but for these risky merge operations validation is only end-of-flow rather than interleaved checkpoints with explicit validate→fix→retry loops, matching the "sequence present but checkpoints implicit" anchor and not the checkpointed level 3. | 2 / 3 |
Progressive Disclosure | A concise overview in SKILL.md points to a single, clearly-signaled, one-level-deep reference ("references/merge-scenarios.md — Detailed examples...") that exists as a real file, matching the well-signaled one-level reference anchor. | 3 / 3 |
Total | 11 / 12 Passed |