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

86%

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

77%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, well-sequenced release runbook with strong validation and recovery paths. Its weaknesses are token efficiency (lengthy prose anecdotes) and a monolithic structure that inlines reference material a separate file could hold.

Suggestions

Tighten the historical anecdotes (e.g. the 0.7.1 drift and v0.3.10 PR-diff stories) to one or two sentences each, keeping the rule but trimming the narrative.

Move the full Homebrew formula template and the deterministic-CI-failure recovery runbook into reference files under ./references/ and link to them one level deep, reducing the inlined wall of content.

Dimension	Reasoning	Score
Conciseness	The 789-line body is mostly efficient and the war-story prose captures institutional knowledge Claude would not already know, but lengthy narrative blocks (e.g. the 0.7.1 drift anecdote, repeated "Why" rationales, the v0.3.10 PR-diff figures) could be tightened without losing the load-bearing guidance.	3 / 5
Actionability	Every step ships concrete, copy-paste-ready bash — `git merge-base --is-ancestor`, the full `homebrew/archon.rb` heredoc, `gh release download` + awk digest verification — covering the common cases with executable commands rather than abstract direction.	5 / 5
Workflow Clarity	Steps 1–12 are explicitly sequenced with mandatory validation checkpoints (Step 1 state validation, Step 1.5 pre-flight smoke, convergence checks), feedback loops (rerun-failed → re-check, fix → re-validate), and a dedicated recovery runbook for deterministic CI failure.	5 / 5
Progressive Disclosure	Headers and numbered steps give the monolithic 789-line body structure, but no bundle files exist and content that would naturally be separate (the full formula template, the recovery runbook) is fully inlined with no one-level-deep references to split it out.	3 / 5
	Total	16 / 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 clearly states capabilities and provides rich, natural trigger phrases. The only gap is that it understates the skill's full scope (tagging, Homebrew formula, tap sync) relative to what the body actually covers.

Dimension	Reasoning	Score
Specificity	"Generates changelog entries from commits, bumps version, and creates a PR to main" names several concrete actions, but tag/homebrew/tap steps from the body are omitted, so it stops short of fully comprehensive coverage.	4 / 5
Completeness	It explicitly states what the skill does (changelog, version bump, PR) and when to use it ("Use this skill when user says:" followed by concrete trigger phrases), cleanly answering both.	5 / 5
Trigger Term Quality	Natural user phrases are comprehensive — "/release", "/release minor", "make a release", "cut a release", "ship it", "release to main" — covering both the slash command and colloquial synonyms users would actually say.	5 / 5
Distinctiveness Conflict Risk	"Create a release from dev branch" with the specific "/release" command and release-to-main triggers carves a clear niche with minimal overlap against other 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: d1ada87

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