Content
93%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 dense, highly actionable runbook: both release lines are covered with executable commands, explicit validation gates, and project-specific conventions that cannot be guessed. The single meaningful gap is the absence of failure-path guidance (what to do when a gate or CI verification fails), which is what keeps workflow clarity at 4.
Suggestions
Add a short failure-path note to the main-product sequence: what to do when a test gate fails or the Docker CI run ends in failure (e.g., delete the local/remote tag and re-tag after the fix), which would raise workflow clarity to 5.
Make the 'notes.md' in the ship step explicit about where it comes from (e.g., extract the vX.Y.Z section of CHANGELOG.en.md into notes.md) so the step is fully self-contained.
State how the two lines interact on a combined release (the release-checklist reference hints at it) — one sentence on ordering would remove the only implicit sequencing in the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries project-specific facts Claude could not infer (root package.json as source of truth, ldflags version injection, HTTP 426 protocol gate, English-only release notes rule). No generic concepts are explained, and the comparison table delivers the two-line structure in minimal tokens. | 5 / 5 |
Actionability | Commands are copy-paste ready throughout: the four pnpm test gates, git tag/push sequence, `gh release create` with flags, `gh run list --limit 3` verification, agent-line `go vet`/`go test`/`sh -n` checks, and a `grep -P '\p{Han}' notes.md` pre-publish check. Placeholders (vX.Y.Z, notes.md) are the only substitutions needed. | 5 / 5 |
Workflow Clarity | The main-product release is a clear numbered sequence (version → changelog → env docs → test gates → ship → verify CI) with explicit checkpoints ("all must pass", run "must end completed/success", grep check). It falls short of 5 because there is no error-recovery guidance — nothing says what to do if a test gate or the CI run fails (e.g., untag/rollback), which matters for an outward-facing publish. | 4 / 5 |
Progressive Disclosure | The body is a compact, well-sectioned overview with clearly signaled one-level-deep pointers ("See `docs/agent/release.en.md` for full details", "Also check `docs/release-checklist.md'"); no bundle files exist to reference, and nothing that belongs elsewhere is inlined. | 5 / 5 |
Total | 19 / 20 Passed |