version-bump-and-changelog

Enforce semantic version bumps and changelog entries in pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/marvelousempire/ai-skills-library --skill version-bump-and-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump-and-changelog
Source: https://github.com/marvelousempire/ai-skills-library/tree/main/skills/methodology/version-bump-and-changelog
Command: npx skills add https://github.com/marvelousempire/ai-skills-library --skill version-bump-and-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the requirement for every Pull Request that changes user-visible or operator-visible behavior to include a version bump and a changelog entry, preventing inconsistencies in the release process.

Core Features & Use Cases

  • Version Control: Automatically updates package versions based on PR changes.
  • Changelog Management: Ensures that each release is documented with relevant changes.
  • Use Case: Before shipping a new version of a software package, this Skill checks that a version bump and a changelog entry have been added, promoting a structured and consistent release process.

Quick Start

When a PR is opened, use the 'version-bump-and-changelog' Skill to automatically check if the version has been bumped and a changelog entry has been added.

Frequently Asked Questions about version-bump-and-changelog

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

FAQPage Schema
How do I enforce a version bump and changelog entry for every pull request?

To enforce a version bump and changelog entry for every pull request, this Skill automatically monitors PRs and verifies that semantic versioning increments and standard changelog formats are included before merging code.

What is the best way to maintain release consistency across multiple software packages?

Maintaining release consistency across software packages requires monitoring version-controlled assets to ensure every PR altering user-visible behavior includes a corresponding version increment and changelog update.

Does this PR management tool require semantic versioning for version increments?

Yes, this PR management tool requires semantic versioning (semver) for all version increments, applying standard changelog formats to code repositories with version-controlled assets to prevent release process inconsistencies.

When do I need to add a changelog entry during the release process?

You need to add a changelog entry during the release process whenever a PR changes user-visible or operator-visible behavior, ensuring each software release is documented with relevant changes before shipping.

Can I use this version bump checker with any code repository?

You can use this version bump checker with code repositories containing version-controlled assets, as it applies standard changelog formats and semver rules to enforce structured release processes.