Content
86%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 a lean, well-sequenced release runbook with concrete commands and appropriate guardrails (user confirmation, the NEVER push --tags warning). Its only weaknesses are minor: the PR-creation step and CHANGELOG restructuring step could be made fully executable, and validation checkpoints after edits are implicit rather than explicit.
Suggestions
Replace "Push the branch and create a PR targeting main" with a concrete command such as `git push -u origin prepare-release-v<version> && gh pr create --base main --title "release: v<version>"`.
Add an explicit validation checkpoint after the edits, e.g. verify with `git diff --stat` that only CHANGELOG.md, lading/Cargo.toml, and Cargo.lock changed before committing, and confirm the new version with `cargo pkgid` or by re-reading Cargo.toml.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every one of the ~45 lines is a concrete instruction; there is no explanation of git, semver, or Cargo basics (the pre-1.0 minor-bump rule is non-inferable project policy), matching the lean/efficient anchor with nothing to trim. | 5 / 5 |
Actionability | Most steps give copy-paste-ready commands (git checkout -b prepare-release-v<version>, cargo check, release: v<version>, git tag -a v<version>), but "Push the branch and create a PR" lacks a concrete command (e.g. gh pr create) and the CHANGELOG restructuring is described rather than exemplified, matching the mostly-executable/minor-gaps anchor. | 4 / 5 |
Workflow Clarity | A clear 7-step numbered sequence with one explicit checkpoint ("Confirm the version with the user before proceeding") and cargo check implicitly validating the lockfile, but there are no verification steps after the CHANGELOG edit or before push and no error-recovery loop, matching the clear-sequence/minor-validation-gaps anchor. | 4 / 5 |
Progressive Disclosure | This is a single-file skill under 50 lines with no need for external references, and the numbered sections are well organized, which per the rubric's simple-skill guideline earns a 5 on well-organized sections alone. | 5 / 5 |
Total | 18 / 20 Passed |