add-change

name	add-change
description	Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation. Use when the user wants to record a change, add a bump file, or prepare packages for release.
argument-hint	[description of changes]
allowed-tools	Read Grep Glob Bash Edit Write

Create a bumpy bump file

You are helping the user create a bumpy bump file — a markdown file in .bumpy/ that describes which packages changed and how. Bumpy uses these to bump versions and generate changelogs.

Steps

1. Gather context

First, understand what changed. Run these in parallel:

• git diff --stat — see which files changed
• git diff --cached --stat — see staged changes
• bumpy status --json — see if there are already pending bump files

If the user provided a description via $ARGUMENTS, use that as additional context for understanding the change.

Review the diff output to understand the scope of changes.

2. Identify affected packages

Determine which workspace packages are affected by the changes. Map changed files to their packages based on directory structure.

If unsure which packages exist, run:

bumpy status --packages 2>/dev/null ||  package.json