prepare-release

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

Quality

96%

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

92%

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

The skill body is highly actionable with a clear, gated workflow and an exact output format. Its main weakness is progressive disclosure: a 170-line single file with no reference bundle, where the detailed release-note specification could be externalized.

Suggestions

Move the bilingual release-note format template and the user-focused-content rules (Step 3) into a `references/release-notes-format.md`, keeping only a concise summary and a clearly-signalled link inline in SKILL.md.

Extract the commit-skip rules and conventional-commit-type extraction (Step 2) into a `references/commit-filtering.md` so the main file reads as an overview.

Split the PR-creation details and CI-trigger chain (Step 6 + 'CI Trigger Chain') into a `references/pr-and-ci.md` to reduce inline length while keeping the core workflow navigable.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable git commands and an exact output-format template; every section is task-specific rather than explaining concepts Claude already knows, so it meets the 'lean and efficient' anchor above the score-2 'could be tightened' level.	3 / 3
Actionability	Provides copy-paste-ready commands (`git describe`, `git log` formats), an exact bilingual template, specific target files, and explicit skip/semver rules — fully executable rather than the pseudocode or abstract guidance at score 2.	3 / 3
Workflow Clarity	Six clearly sequenced steps with an explicit confirm checkpoint (Step 5) before the destructive branch/PR step, plus a dry-run preview and review checklist; the presence of a gate means it is not capped at 2 for missing validation.	3 / 3
Progressive Disclosure	Sections are well organized but no bundle/reference files exist, and the large inline Step 3 format template plus user-focused rules (~70 lines) is content that should arguably live in a separate reference file — matching the score-2 'content that should be separate is inline' anchor rather than the split, signalled structure of score 3.	2 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is strong: third-person, specific, with an explicit 'Use when...' trigger clause covering natural phrasings. It clearly states both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR' — matching the score-3 anchor rather than the partial score-2 example.	3 / 3
Completeness	Explicitly answers both what (collect→generate→update→branch+PR) and when ('Use when asked to prepare/create a release, bump version, or run `/prepare-release`'), with an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural phrases a user would say — 'prepare/create a release', 'bump version', '/prepare-release' — give good coverage; not merely jargon, so it sits above the score-2 'some relevant keywords' anchor.	3 / 3
Distinctiveness Conflict Risk	A clear niche — Cherry Studio bilingual release preparation — with distinct triggers unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: about 13 hours 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.