You are in AUTONOMOUS MODE. Do NOT ask questions. Do NOT pause for confirmation. Execute every phase below in sequence, making decisions based on what you find.
============================================================ PHASE 0 — INPUT
$ARGUMENTS may contain:
--tool=TOOL— force a specific release tool:semantic-release,changesets,release-please,cargo-release,goreleaser--publish=TARGET— where to publish:npm,pypi,crates,ghcr,github(GitHub Releases only)--monorepo— configure for monorepo with independent package versioning--dry-run— generate config files but do not create any CI workflows--channel=CHANNEL— set release channel:latest(default),next,beta,alpha
If no arguments, auto-detect the best tool and target.
============================================================ PHASE 1 — STACK DETECTION
Detect the project stack and current release state:
Language & Package Registry:
package.json→ npm (checkpublishConfig,privatefield,namescope)pyproject.toml→ PyPI (check[project]or[tool.poetry]section)Cargo.toml→ crates.io (checkpublishfield)go.mod→ Go modules (tag-based releases)pubspec.yaml→ pub.dev (checkpublish_to)
Current Versioning:
- Read current version from manifest file
- Check git tags:
git tag --list 'v*' --sort=-version:refname | head -5 - Check if CHANGELOG.md exists and its format (Keep a Changelog, conventional, custom)
- Check existing release CI workflows in
.github/workflows/
Monorepo Detection:
turbo.json/nx.json/pnpm-workspace.yaml/lerna.json- Multiple
package.jsonfiles in subdirectories - If monorepo detected, prefer changesets over semantic-release
Existing Commit Convention:
- Check if commitlint is configured (conventional commits already enforced)
- Sample recent commits:
git log --oneline -20to see if they follow a pattern - Check for
.husky/commit-msgor equivalent hook
Record: language, registry, current version, monorepo status, commit convention.
============================================================ PHASE 2 — SELECT AND CONFIGURE RELEASE TOOL
If Node.js single-package → semantic-release:
Install:
npm install --save-dev semantic-release @semantic-release/changelog @semantic-release/gitCreate
.releaserc.json:{ "branches": ["main"], "plugins": [ "@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", ["@semantic-release/changelog", { "changelogFile": "CHANGELOG.md" }], ["@semantic-release/npm", { "npmPublish": true }], ["@semantic-release/git", { "assets": ["CHANGELOG.md", "package.json"], "message": "chore(release): ${nextRelease.version}" }], "@semantic-release/github" ] }Adjust: set
"npmPublish": falseifpackage.jsonhas"private": true. If--channelspecified, add branch config for pre-release channels.If commitlint is NOT already set up, install it:
npm install --save-dev @commitlint/cli @commitlint/config-conventionalCreate
commitlint.config.js:export default { extends: ['@commitlint/config-conventional'] };
If Node.js monorepo → changesets:
- Install:
npm install --save-dev @changesets/cli @changesets/changelog-github - Initialize:
npx changeset init - Configure
.changeset/config.json:
Detect repo name from{ "$schema": "https://unpkg.com/@changesets/config@3.0.0/schema.json", "changelog": ["@changesets/changelog-github", { "repo": "{owner}/{repo}" }], "commit": false, "fixed": [], "linked": [], "access": "public", "baseBranch": "main", "updateInternalDependencies": "patch", "ignore": [] }git remote get-url origin.
If Python → semantic-release (Python):
- Install:
pip install python-semantic-release(or add to dev dependencies) - Add to
pyproject.toml:
If publishing to PyPI, add:[tool.semantic_release] version_toml = ["pyproject.toml:project.version"] branch = "main" commit_message = "chore(release): {version}" build_command = "pip install build && python -m build"upload_to_pypi = true
If Go → goreleaser:
- Install config: create
.goreleaser.yml:version: 2 builds: - env: [CGO_ENABLED=0] goos: [linux, darwin, windows] goarch: [amd64, arm64] archives: - format: tar.gz name_template: "{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_{{ .Arch }}" format_overrides: - goos: windows format: zip changelog: sort: asc filters: exclude: ["^docs:", "^test:", "^chore:"]
If Rust → cargo-release:
- Install:
cargo install cargo-release - Add to
Cargo.toml:[workspace.metadata.release] sign-commit = false sign-tag = false push = true publish = true
If release-please requested:
- Create
.release-please-manifest.json:{ ".": "0.1.0" } - Create
release-please-config.json:{ "packages": { ".": { "release-type": "{node|python|go|...}" } }, "changelog-sections": [ { "type": "feat", "section": "Features" }, { "type": "fix", "section": "Bug Fixes" }, { "type": "perf", "section": "Performance" }, { "type": "docs", "section": "Documentation" } ] }
============================================================ PHASE 3 — GENERATE CI WORKFLOW
Skip if --dry-run was passed.
Create .github/workflows/release.yml:
For semantic-release:
name: Release
on:
push:
branches: [main]
permissions:
contents: write
issues: write
pull-requests: write
packages: write
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
persist-credentials: false
- uses: actions/setup-node@v4
with:
node-version: 20
cache: npm
- run: npm ci
- run: npx semantic-release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
For changesets:
name: Release
on:
push:
branches: [main]
permissions:
contents: write
pull-requests: write
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
cache: npm
- run: npm ci
- uses: changesets/action@v1
with:
publish: npm run release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
For release-please:
name: Release
on:
push:
branches: [main]
permissions:
contents: write
pull-requests: write
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v4
with:
release-type: node
For goreleaser:
name: Release
on:
push:
tags: ['v*']
permissions:
contents: write
jobs:
goreleaser:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-go@v5
with:
go-version-file: go.mod
- uses: goreleaser/goreleaser-action@v6
with:
args: release --clean
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Adjust for Python/Rust equivalents as appropriate.
============================================================ PHASE 4 — VERIFY CONFIGURATION
- Validate the release config file is syntactically correct (parse JSON/YAML/TOML)
- Verify conventional commits are being enforced (commitlint or equivalent is configured)
- Dry-run the release tool if supported:
- semantic-release:
npx semantic-release --dry-run - changesets:
npx changeset status - goreleaser:
goreleaser check
- semantic-release:
- Verify the CI workflow YAML is valid
- Check that required secrets are documented
============================================================ SELF-HEALING VALIDATION (max 2 iterations)
After completing, validate the output was produced correctly:
- Verify generated files exist and are syntactically valid.
- Run any available validation (lint, type-check, dry-run).
- If the skill produces configuration, verify it parses without errors.
IF VALIDATION FAILS:
- Diagnose from error context and re-generate the failing artifact
- Repeat up to 2 iterations
============================================================ OUTPUT
Print a summary:
## Release Pipeline Setup Complete
### Tool: {semantic-release | changesets | release-please | goreleaser | cargo-release}
### Current Version: {version}
### Publish Target: {npm | pypi | crates.io | GitHub Releases}
### Release Channel: {latest | next | beta}
### How It Works
1. Write code using conventional commits (feat:, fix:, etc.)
2. Push/merge to main
3. {tool} analyzes commits since last release
4. Automatically: bumps version, generates changelog, creates git tag, publishes
### Commit → Release Mapping
- `feat:` → minor version bump (0.1.0 → 0.2.0)
- `fix:` → patch version bump (0.1.0 → 0.1.1)
- `feat!:` or `BREAKING CHANGE:` → major version bump (0.1.0 → 1.0.0)
- `docs:`, `chore:`, `ci:` → no release
### Files Created/Modified
- {list of files}
### Required Secrets
- GITHUB_TOKEN: automatic (provided by GitHub Actions)
- NPM_TOKEN: {required if publishing to npm — generate at npmjs.com}
- {other secrets as applicable}
============================================================ NEXT STEPS
- Add required secrets to GitHub repository settings (Settings → Secrets → Actions)
- Run
/git-hooksto enforce conventional commits locally if not already set up - Make a
feat:commit and push to main to trigger the first release - For monorepos: run
npx changesetbefore merging PRs to document changes
============================================================ SELF-EVOLUTION TELEMETRY
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
- Look for the project path in
~/.claude/projects/ - If found, append to
skill-telemetry.mdin that memory directory
Entry format:
### /release — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
============================================================ DO NOT
- Do NOT configure publishing for private packages unless explicitly requested
- Do NOT use
GITHUB_TOKENfor npm publishing — it requires a separateNPM_TOKEN - Do NOT set up multiple release tools that conflict (e.g., semantic-release AND changesets)
- Do NOT skip conventional commit enforcement — releases depend on structured commit messages
- Do NOT use
fetch-depth: 1in the release workflow — semantic-release needs full git history - Do NOT overwrite existing CHANGELOG.md — the release tool will manage it going forward
- Do NOT use deprecated action versions (checkout@v2, setup-node@v3, etc.)
- Do NOT publish to registries during dry-run verification