Content
75%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.
A highly actionable, well-structured operational skill with copy-paste-ready commands and a clear read-back workflow. Its main weakness is conciseness: dated historical anecdotes and ledger-archaeology details are inlined where a leaner rule statement (or a separate history/deprecated reference) would serve better.
Suggestions
Move dated history — the ISSUES-LIST.html retirement (2026-08-18), the PR #1766/#1767 duplicate anecdote, and the #M6JNR8 pruning limitation — into a short 'History / deprecated' section or reference file, keeping only the currently applicable rule in the main flow.
Tighten the 'A row being open is not evidence that nobody is working on it' paragraph down to its actionable rule: before acting on a queued item, check open PRs for the touched route/component; drop the narrative example.
Sequence the validation into the mutation workflow as an explicit checkpoint (after queueing a request, run `npm run issues:check`-style verification and fix/retry), rather than leaving it as a standalone bullet in Writing rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient operational guidance, but several passages carry dated historical rationale — the legacy ISSUES-LIST.html retirement ("retired on 2026-08-18"), the duplicate-PR anecdote ("PR #1766 and the duplicate PR #1767, four hours apart, 2026-08-09"), "until ledger #M6JNR8" — that could be tightened or moved to a deprecated/history section. Not 4 because these history blocks are more than minor trimming; not 2 because the core instructions themselves are dense and earn their tokens. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover the common cases: `npm run issues:report -- --json`, the full issues:add/done/update/queue invocations with flags, and explicit-path git add/commit lines, plus concrete filters (`/issues P1`, `--agent-safe-wins`). | 5 / 5 |
Workflow Clarity | The default read is a clear numbered 5-step sequence with an explicit no-mutation checkpoint, and a validation gate (`npm run check:outstanding-issues`) exists. Not 5 because that validation step is not sequenced into the mutation flows — it appears in Writing rules rather than as an explicit post-write checkpoint with a fix-and-retry loop. | 4 / 5 |
Progressive Disclosure | Well-organized single-file skill with clear sections (Trigger, Default, Mutating subcommands, Capture discipline, Writing rules, canonical ledger, commit); no bundle files exist and none are needed for the core flow. Not 5 because the body exceeds a lean overview — the historical rationale sections (legacy register retirement, duplicate-PR policy) would fit better in a separate reference file. | 4 / 5 |
Total | 16 / 20 Passed |