stave-release

Release workflow for the Stave repository that confirms whether the next release is patch or minor before bumping the version, reviews the actual PR changes and PR description `Changes` sections in the release scope instead of relying on commit titles alone, generates release notes with `conventional-changelog`, and opens a pull request against `main` from a dedicated temporary release worktree so the user's original checkout stays on its original branch. Use when the user asks to cut the next release, ship the current changes as a versioned release, or prepare a release PR. After the PR merges, the repository's GitHub Actions workflow builds and publishes the release artifacts automatically.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

A well-engineered instruction skill: concrete commands, clear multi-step sequencing with validation and recovery, and a clean one-level reference split. Minor redundancy between the body's workflow and the bundled checklist is the only nit.

Dimension	Reasoning	Score
Conciseness	Lean, imperative body with concrete commands and no explanations of concepts Claude already knows; every step earns its place, though the workflow steps overlap somewhat with the bundled checklist.	3 / 3
Actionability	Provides fully executable git/gh/bunx commands, explicit version-bump arithmetic, exact worktree paths, and copy-paste-ready PR creation commands.	3 / 3
Workflow Clarity	Ten-step sequence with explicit validation checkpoints (clean tree, origin, typecheck, post-open PR diff review) and feedback loops (stop on unrelated work, retry worktree remove after correcting cwd) for a destructive/batch operation.	3 / 3
Progressive Disclosure	Opens with a concise overview and a single well-signaled, one-level-deep reference (references/stave-release-checklist.md, verified present) for the exact sequence and repair rules.	3 / 3
	Total	12 / 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.

A strong description that pairs concrete capability statements with explicit, naturally-worded use-when triggers scoped to a specific repository release workflow. It answers what, when, and how without padding or vague claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (confirm patch/minor bump, review PR Changes sections, generate notes via conventional-changelog, open a PR from a temp worktree) rather than vague language.	3 / 3
Completeness	Explicitly states what the skill does and includes a 'Use when...' clause with explicit triggers covering both what and when.	3 / 3
Trigger Term Quality	Uses natural user phrasings like 'cut the next release', 'ship the current changes as a versioned release', and 'prepare a release PR' that a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to the Stave repository's release process with a distinct, repo-specific trigger set, making it unlikely to fire for unrelated skills.	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: sendbird/stave
Commit: 8e1e80c

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