release-management

Executes SemVer version bumps, changelog updates, and release commits with pre-release test verification.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill release-management-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/release-management
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill release-management-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a software release involves many error-prone manual steps: choosing the right SemVer bump, running the full test suite, syncing version numbers across manifests, updating the changelog, and pushing commits and tags. This Skill standardizes that entire ceremony into a repeatable, verifiable workflow. ## Core Features & Use Cases - SemVer Version Bumping: Determines the bump tier (MINOR by default, resetting PATCH to 0) and synchronizes the version across package.json and related manifests via npm run sync. - Mandatory Pre-Release Verification: Runs the local CI/CD test runner and cross-references recent file changes against the test inventory to confirm all affected suites pass before releasing. - Changelog & Atomic Commit: Prepends a verified changelog entry, then creates a single grouped release commit and pushes the branch and tags to origin. - Use Case: When finishing a sprint, invoke this Skill to bump the project from 2.1.4 to 2.2.0, verify all tests pass, update the changelog, and push the release in one guided flow. ## Quick Start Run the release-management skill to bump the minor version, verify all tests pass, update the changelog, and push the release commit to origin.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I bump a SemVer version and update the changelog automatically?

Determine the bump tier (MINOR by default, resetting PATCH to 0), update the version in package.json, run npm run sync to propagate it, then prepend a verified entry to changelog.md before committing and pushing.

What steps should run before creating a software release?

Run the full unit test suite via the local CI/CD runner and confirm all quality gates pass with exit code 0. Then cross-reference recently changed files against the test inventory to verify every affected suite is green.

Should I create a git tag manually during a release?

No, do not create a manual git tag if tagging is managed externally by your release infrastructure. The workflow only requires committing the version bump and pushing the branch and tags to origin.

Why should release changes be a single commit instead of per-file commits?

Grouping all modified files into one atomic commit keeps the release history clean and ensures the version bump, changelog, and synced manifests land together. Per-file commits fragment the release and complicate rollbacks.

Can the release run if some tests are failing?

Standard releases require all test suites and quality gates to pass 100% green. An emergency path exists using the CI runner's --skip-tests flag, but it is reserved for exceptional situations only.