prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable release-prep workflow with strong validation checkpoints and executable commands throughout. Its only weaknesses are minor verbosity from repeated git checks and long CI-chain prose, and the absence of any progressive disclosure to bundle files.

Suggestions

Extract the detailed 'CI Trigger Chain' section (and possibly the bilingual release-note template) into a reference file under references/ and link to it from SKILL.md to reduce inline length and improve progressive disclosure.

De-duplicate the git fetch/clean-worktree verification between Step 1 and Step 6 by referencing a shared named check rather than restating the full block, tightening conciseness.

Shorten the long compound sentences in the CI Trigger Chain into bulleted, single-responsibility statements to improve scannability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural commands and project-specific policy rather than concepts Claude already knows, but the Step 1 git checks are repeated in Step 6 and the CI Trigger Chain uses long compound sentences that could be trimmed, keeping it just below the lean anchor 5.	4 / 5
Actionability	Fully executable bash blocks for fetch/verify/commit/push, specific file paths, concrete validator invocations like `node scripts/release/sync-release-history.js --target-version {version}`, and a copy-paste-ready release-note template cover the common cases per anchor 5.	5 / 5
Workflow Clarity	Steps 1-6 are explicitly sequenced with extensive validation checkpoints ('Stop before editing files if any check fails', `validate-prepared-release.js`) and a validate-fix-retry feedback loop, matching anchor 5 for a destructive/batch operation with full validation.	5 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is well-sectioned (Arguments, Workflow, CI Trigger Chain, Constraints), but at ~213 lines it exceeds the simple-skill threshold and keeps detailed sub-content like the CI trigger chain and release-note template fully inlined, so it sits at the good-structure anchor 4 rather than a clean overview with one-level-deep references.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that clearly states both the capability and the natural trigger conditions, with a distinctive slash-command trigger. Only trigger-term breadth is slightly limited by missing common release synonyms.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'collecting commits, generating bilingual release notes, updating version files, and creating a release branch' — giving comprehensive coverage of the release-prep workflow rather than the 1-2 actions of anchor 3 or the minor-gap coverage of anchor 4.	5 / 5
Completeness	Explicitly answers what (the four release-prep actions) and when ('Use when asked to prepare/create a release, bump version, or run `/prepare-release`') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural triggers like 'prepare/create a release', 'bump version', and the slash command `/prepare-release` give good keyword coverage, but common synonyms such as 'cut a release', 'ship a release', or 'changelog' are absent, so it falls short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The release-prep niche plus the unique `/prepare-release` slash-command trigger make it clearly distinguishable from other skills with minimal conflict risk, matching anchor 5.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing, 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: CherryHQ/cherry-studio
Path: .agents/skills/prepare-release/SKILL.md
Commit: 1219558

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.