How do I install the Release Management skill?

Run npx skillmds@latest add sgcarstrends/release-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Management safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Management?

sgcarstrends (@sgcarstrends) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Management by sgcarstrends — Agent Skill

Name: Release Management
Rating: 4.2 (5 reviews)
Author: sgcarstrends

File contents

Release Management Skill

Automated releases via semantic-release with unified "v" prefix versioning.

How It Works

Commits pushed to main trigger .github/workflows/release.yml
Checks run first (test + lint matrix)
semantic-release analyses commits since last tag
Version bumped based on commit types (see conventional-commits skill)
CHANGELOG.md updated automatically
All package.json files updated across the monorepo (pnpm -r exec -- npm version)
Git tag created with v prefix (e.g., v4.46.0)
GitHub Release created with auto-generated notes
Release commit created: chore(release): v{version} [skip ci]
Vercel auto-deploys the new version

Version Scheme

Format: v{major}.{minor}.{patch} (e.g., v4.46.0)
Unified version across the entire monorepo
Tag format configured in .releaserc.json: "tagFormat": "v${version}"

Configuration

.releaserc.json plugins:

@semantic-release/commit-analyzer — conventionalcommits preset
@semantic-release/release-notes-generator — conventionalcommits preset
@semantic-release/changelog — writes CHANGELOG.md
@semantic-release/exec — bumps all package.json versions
@semantic-release/git — commits changelog + package.json changes
@semantic-release/github — creates GitHub Release, adds "released" label

Checking Release Status

# View recent releases
gh release list --limit 5

# View specific release
gh release view v4.46.0

# Check release workflow status
gh run list --workflow=release.yml --limit 5

# View release workflow logs
gh run view <run-id> --log

Debugging Release Failures

Release Not Triggered

Verify commit type is feat or fix (not chore, docs, etc.)
Check workflow ran: gh run list --workflow=release.yml
Verify branch is main

Version Not Bumped

Check commit message format matches conventional commits
Look for [skip ci] in commit message (release commits include this)

Workflow Failed

Check GitHub Actions logs: gh run view <run-id> --log
Common causes: test failures, lint errors, npm publish issues

Manual Release (Emergency Only)

# Create tag manually
git tag -a v4.47.0 -m "v4.47.0"
git push origin v4.47.0

# Create GitHub release from tag
gh release create v4.47.0 --generate-notes

See conventional-commits skill for commit message format
See changelog skill for changelog details
See deployment-rollback skill for rolling back releases
Workflow: .github/workflows/release.yml
Config: .releaserc.json

---name: release-managementdescription: Manage releases with semantic-release, version bumps, and changelog generation. Use when preparing releases, debugging release failures, or understanding version history.---# Release Management SkillAutomated releases via semantic-release with unified "v" prefix versioning.## How It Works1. Commits pushed to `main` trigger `.github/workflows/release.yml`2. Checks run first (test + lint matrix)3. semantic-release analyses commits since last tag4. Version bumped based on commit types (see `conventional-commits` skill)5. `CHANGELOG.md` updated automatically6. All `package.json` files updated across the monorepo (`pnpm -r exec -- npm version`)7. Git tag created with `v` prefix (e.g., `v4.46.0`)8. GitHub Release created with auto-generated notes9. Release commit created: `chore(release): v{version} [skip ci]`10. Vercel auto-deploys the new version## Version Scheme- Format: `v{major}.{minor}.{patch}` (e.g., `v4.46.0`)- Unified version across the entire monorepo- Tag format configured in `.releaserc.json`: `"tagFormat": "v${version}"`## Configuration**`.releaserc.json`** plugins:1. `@semantic-release/commit-analyzer` — conventionalcommits preset2. `@semantic-release/release-notes-generator` — conventionalcommits preset3. `@semantic-release/changelog` — writes `CHANGELOG.md`4. `@semantic-release/exec` — bumps all package.json versions5. `@semantic-release/git` — commits changelog + package.json changes6. `@semantic-release/github` — creates GitHub Release, adds "released" label## Checking Release Status```bash# View recent releasesgh release list --limit 5# View specific releasegh release view v4.46.0# Check release workflow statusgh run list --workflow=release.yml --limit 5# View release workflow logsgh run view <run-id> --log```## Debugging Release Failures### Release Not Triggered- Verify commit type is `feat` or `fix` (not `chore`, `docs`, etc.)- Check workflow ran: `gh run list --workflow=release.yml`- Verify branch is `main`### Version Not Bumped- Check commit message format matches conventional commits- Look for `[skip ci]` in commit message (release commits include this)### Workflow Failed- Check GitHub Actions logs: `gh run view <run-id> --log`- Common causes: test failures, lint errors, npm publish issues## Manual Release (Emergency Only)```bash# Create tag manuallygit tag -a v4.47.0 -m "v4.47.0"git push origin v4.47.0# Create GitHub release from taggh release create v4.47.0 --generate-notes```## Related- See `conventional-commits` skill for commit message format- See `changelog` skill for changelog details- See `deployment-rollback` skill for rolling back releases- Workflow: `.github/workflows/release.yml`- Config: `.releaserc.json`

Frequently asked questions

Release Management