skills.rest
sgcarstrends
sgcarstrendsOFFICIAL
Explore all skills by this author →
GitHub

release-management

Automate software release workflows with semantic-release and conventional commits.

21|2|Updated Nov 5, 2023
Search Tags:#versioning#semantic-release#CI#release-notes#github-releases#git-tags
One-click install
npx skills add https://github.com/sgcarstrends/sgcarstrends --skill release-management-sgcarstrends
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/sgcarstrends/sgcarstrends/tree/main/.claude/skills/release-management
Command: npx skills add https://github.com/sgcarstrends/sgcarstrends --skill release-management-sgcarstrends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates releases using semantic-release, generates release notes, manages versions, and optionally publishes packages, reducing manual release overhead.

Core Features & Use Cases

  • Semantic Release: Automatic version bumps based on conventional commits.
  • Changelog & Tags: Auto-generated changelog and GitHub releases with notes.
  • Publishing: Optional publishing to npm or registries.

Quick Start

Push changes to main to trigger an automated release with npx semantic-release or configure a workflow to run on merge.

Frequently Asked Questions about release-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps and releases in my CI/CD pipeline?▼

Semantic-release automatically bumps versions based on conventional commits, generates changelogs, creates Git tags, and publishes GitHub releases. Push to main to trigger the workflow with npx semantic-release or configure it in your CI pipeline to run on merge.

Can I generate release notes automatically from my Git commits?▼

Yes, semantic-release reads conventional commits from your history and auto-generates release notes with categorized changes. These notes are published to GitHub releases alongside version tags without manual editing.

What's the difference between semantic versioning and manual release management?▼

Semantic versioning derives version numbers from commit types—breaking changes bump major, features bump minor, fixes bump patch. This eliminates human guesswork and keeps releases consistent across projects and teams.

Do I need to manually publish packages after semantic-release creates a version?▼

No. Semantic-release can optionally publish to npm or other registries automatically after tagging. Configure publishing credentials in your CI environment to push releases without manual steps.

What commit format does semantic-release require?▼

Semantic-release follows conventional commits: commit messages like `feat: new feature` or `fix: bug fix` trigger version bumps. Titles starting with `BREAKING CHANGE:` bump major versions. Tools that enforce this format integrate seamlessly with the workflow.

Related Skills

Explore More Product & Management Skills→
nickromneynickromney

Setup Semantic Release

Automate version bumps, changelog updates, and publishing from conventional commits.

Community
Advanced
tethertotetherto
395

release

Automate NPM package releases by validating versions, updating changelogs, and creating release branches.

Official
Advanced
coreindustriescoreindustries
1

release

Tag new versions, generate changelogs from conventional commits, and create GitHub releases.

Community
Advanced
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced