Automate Agent-Driven Releases with skillshare-release

Where this fits

After the last feature branch merges to main, you tell your agent: release v0.19.0. What should happen next is not just a version bump — it is a sequence: tests must pass, changelog must be generated from commits, version files updated, commit made, and announcement drafted. The skillshare-release skill encodes that release workflow so the agent can execute it end-to-end instead of asking you what to do.

Why agents benefit

• It knows when to use /changelog for changelog-only requests and when to run the full release workflow, so it does not overstep on simple tasks.
• It runs make check first and fixes failures without prompting, eliminating a common stalled-agent loop.
• It parses conventional commits to categorize changes, removing manual changelog editing.
• It requires a version argument and validates a clean working directory upfront, catching common release mistakes before they happen.
• It sequences commit and announcement steps automatically, leaving the only necessary decision to the user: the version number.

Practical scenarios

Cutting a patch release after a hotfix

Suppose you have a hotfix on main and say release v0.19.1. The agent checks for uncommitted changes, runs the full check suite, uses /changelog v0.19.1 to draft release notes, bumps the version, commits the release, and leaves a drafted announcement.

Coordinating a planned minor release

Before a sprint demo, you ask prepare release v0.20.0. The agent catches a failing lint rule, fixes it, re-runs make check, then proceeds with changelog generation and version updates — no need to babysit.

Routing a changelog-only request

Your colleague only wants release notes for the current main branch. If they ask generate changelog, the skill routes to /changelog instead of accidentally cutting a release.

Add it to your agent workflow

Install with:

npx skills add runkids/skillshare --skill skillshare-release

Then invoke it with a version: release v0.19.0 or prepare release v0.19.0. The argument-hint expects the version string, so include it in the request.

Compare before adopting

Before adding this skill, compare it with what you already run. Do you have a release script that builds on make check? Does your team use conventional commits for changelog generation? Evaluate quality signals like the skill’s test suite, CI status, and how recent the repository is. Also check workflow fit: this skill expects a clean working directory and a linear validate → changelog → version → commit → announce sequence. If your release process includes manual QA or external approvals, you may need to adapt the surrounding workflow. For a compact overview of the skill, see https://www.openagentskill.com/skills/runkids-skillshare-release.

Why it is worth tracking

The repository has 2,600+ stars, which suggests active use, but popularity alone should not decide adoption. Watch how quickly the author responds to issues and how often the skill definition is updated for new agent runtimes. Since agent release workflows evolve quickly, re-evaluate this skill whenever you change your versioning scheme or add a new announcement channel — it is a useful baseline for automated releases and a good example of a well-scoped agent skill.