add-change

Generate bump files documenting package changes for software releases.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/AndersCan/mantaq --skill add-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-change
Source: https://github.com/AndersCan/mantaq/tree/main/.opencode/skills/add-change
Command: npx skills add https://github.com/AndersCan/mantaq --skill add-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bumpy, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating bump files, which record changes for package releases, reducing manual effort and streamlining release preparation.

Core Features & Use Cases

  • Automated Bump File Creation: Generate bump files that capture package changes, ensuring release documentation is kept up to date.
  • Change Summarization: Simplify the process of summarizing changes for CHANGELOG entries with best practices guidance.
  • Use Case: After merging code changes, use this Skill to generate bump files that capture all changes, automatically creating the necessary documentation for the next release.

Quick Start

Execute the skill with the description of your changes to generate a bump file.

Frequently Asked Questions about add-change

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

FAQPage Schema
How do I automate bump file creation for package releases?

Automating bump file creation for package releases is handled by generating files that capture code changes and summarizing them for CHANGELOG entries. You execute the skill with a description of your changes to automatically create the necessary release documentation.

What is a bump file and when do I need it for release preparation?

A bump file is a record of changes made for a software package release. You need it during release preparation to identify affected packages and document change summaries, ensuring your CHANGELOG is kept up to date without manual effort.

Do I need the bumpy tool to manage bump files for my changes?

Yes, you need the bumpy tool to manage bump files. The skill requires bumpy for bump file management and supports common package structures and workflows to streamline your release preparation process.

How do I summarize changes for a CHANGELOG after merging code?

Summarizing changes for a CHANGELOG after merging code is done by generating a bump file that captures all package changes. The skill provides best practices guidance to simplify creating accurate change summaries for your release documentation.

What's the best way to prepare documentation for a package release?

Preparing documentation for a package release is best done by automating bump file generation. This approach identifies affected packages and documents change summaries directly from your merged code, reducing manual effort and streamlining the release workflow.