release

Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"

Quality

82%

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

70%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.

An exceptionally actionable and well-sequenced release runbook with strong validation and recovery flows, undermined mainly by verbosity and a monolithic structure that offloads nothing to reference files. Tightening the war-story prose and splitting the formula template / recovery procedure into referenced files would lift the weaker dimensions.

Suggestions

Move the inline historical anecdotes (e.g. the 0.7.1 '61 vs 25 commits' and v0.3.10 reset war stories) into a brief 'Past incidents' reference, or compress them to one-line rationale so time-sensitive version numbers stop padding the main flow.

Extract the full Homebrew formula template and the deterministic-CI-failure recovery procedure into one-level-deep reference files (e.g. references/formula.rb, RECOVERY.md) referenced from the steps, improving progressive disclosure and trimming the main body.

Convert the long blockquote 'why' asides (the --no-rebase, ff-only/reset, and clean-merge-not-proof explanations) into terse imperative notes, keeping the rule in the Important Rules checklist and dropping the narrative justification.

Dimension	Reasoning	Score
Conciseness	At ~775 lines the body is noticeably verbose: many long blockquote rationale asides and inline war stories carry time-sensitive version numbers and PR numbers (0.7.1, 0.3.10, #2155) that the rubric penalizes unless isolated in a deprecated/old-patterns section, and the prose could be substantially tightened without losing the actionable core.	2 / 5
Actionability	Fully executable guidance throughout — concrete `git`/`gh` commands, a complete regenerable Homebrew formula template, and ready-to-run bash blocks (asset polling, checksum extraction, formula verification) covering the common cases.	5 / 5
Workflow Clarity	A clear Step 1→12 sequence with explicit validation checkpoints and fail-closed convergence checks, error-recovery feedback loops (Step 10 rerun + the dedicated Recovery section), and an Important Rules checklist for a destructive/batch operation.	5 / 5
Progressive Disclosure	The file is well-sectioned by step, but it is a monolithic single file with no bundle references; the recovery procedure, full formula template, and commit-boundary derivation logic are candidates for one-level-deep reference files that remain inline.	3 / 5
	Total	15 / 20 Passed

Description

95%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 strong, third-person description that explicitly pairs a concrete capability statement with a rich, natural-language trigger list. Its only weakness is that the 'what' understates the skill's full scope (homebrew formula, tap sync, end-to-end verification) relative to the body.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('Generates changelog entries from commits, bumps version, and creates a PR to main'), but omits the homebrew-formula, tap-sync, and test-release work the body covers, leaving minor gaps.	4 / 5
Completeness	Clearly answers both 'what' (first sentence) and 'when' (explicit 'TRIGGERS - Use this skill when user says' list with concrete phrases), in third-person voice.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases with synonyms — '/release', '/release minor', '/release major', 'make a release', 'cut a release', 'ship it', 'release to main' — that users would actually say.	5 / 5
Distinctiveness Conflict Risk	A clear release-from-dev niche with distinct triggers ('/release', 'cut a release', 'ship it') that are unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (789 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: coleam00/Archon
Path: .claude/skills/release/SKILL.md
Commit: e237584

Reviewed: 5 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.