New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bumpy Add Change

by zap-studio in zap-studio/monorepo

Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation.

MITAuto-check: notesDevelopment

Install Bumpy Add Change

skills CLI
$ npx skills add zap-studio/monorepo --skill bumpy-add-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zap-studio/monorepo bumpy-add-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zap-studio/monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bumpy-add-change .claude/skills/bumpy-add-change && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bumpy-add-change
GitHub stars
172
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
635 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation.

  • Works in 5 steps: Gather context → Identify affected packages → Determine bump levels → …
  • The user wants to record a change
  • SKILL.md covers Steps, Advanced: cascading bumps, Advanced: omitting an entry… and Important notes
  • Calls git

What it does

Bumpy Add Change is an agent skill from zap-studio/monorepo. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes, Monorepo tooling and Type safety. It works with TypeScript. The repository describes itself as: Type-safe, framework-agnostic, composable, and tree-shakeable TypeScript libraries for the web. The licence is MIT.

When your agent uses it

  • The user wants to record a change
  • Add a bump file
  • Prepare packages for release

Example prompts

  • “/bumpy-add-change”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Edit, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather context
  2. Identify affected packages
  3. Determine bump levels
  4. Write a clear summary
  5. Create or update the bump file

What it can do on your machine

Read from SKILL.md and the folder at commit 8dd89f1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • Edit
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bumpy Add Change loads about 1.4k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 635 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, Edit, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zap-studio/monorepo at commit 8dd89f1, republished under its MIT licence (© zap-studio). 635 words, ~1,394 tokens.

Download SKILL.mdSave it as .claude/skills/bumpy-add-change/SKILL.md (or your agent's skills folder).
name
bumpy-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.
allowed-tools
Read, Grep, Glob, Bash, Edit, Write
argument-hint
[description of changes]

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:

bash
bumpy status --packages 2>/dev/null || cat package.json
3. Determine bump levels

For each affected package, choose the appropriate bump level:

LevelWhen to use
majorBreaking changes: removed/renamed exports, changed function signatures, dropped support
minorNew features: added exports, new options, new functionality
patchBug fixes, internal refactors, documentation, dependency updates

Use none in a bump file to acknowledge a change without triggering a direct bump. Cascading bumps from other packages can still apply normally.

4. Write a clear summary

Write a concise summary for the CHANGELOG entry. Keep it short — ideally a single sentence, at most two. Good summaries:

  • Start with a verb: "Added...", "Fixed...", "Refactored..."
  • Focus on user-facing impact, not implementation details
  • Are specific enough to be useful months later
  • Avoid filler, jargon, or restating the bump level
  • Don't list every file changed — describe the logical change

Bad: "Updated the authentication module to fix an issue where the token refresh mechanism was not properly handling expired refresh tokens, causing silent failures in the auth flow." Good: "Fixed token refresh failing silently on expired refresh tokens."

5. Create or update the bump file

Check if there are already bump files on this branch (from step 1's bumpy status). If one exists that covers the same logical change, update it in place by editing the .bumpy/<name>.md file directly — adjust the package list, bump levels, and summary to reflect the current state of the branch. Don't create a new bump file for every incremental change on the same branch.

If no relevant bump file exists yet, create one with the non-interactive CLI:

bash
bumpy add \
  --packages "<pkg1>:<bump>,<pkg2>:<bump>" \
  --message "<summary>" \
  --name "<short-descriptive-name>"

The --name should be a short kebab-case slug describing the change (e.g., fix-auth-token-refresh, add-encryption-api).

Show full SKILL.md (238 more words)Show less
Example

If the user fixed a bug in @myorg/auth that also required a type change in @myorg/types:

bash
bumpy add \
  --packages "@myorg/auth:patch,@myorg/types:patch" \
  --message "Fixed token refresh failing silently when the refresh token has expired." \
  --name "fix-token-refresh"

Advanced: cascading bumps

If a change in a core package should explicitly cascade to dependents with specific bump levels, write the bump file directly instead of using the CLI:

bash
cat > .bumpy/<name>.md << 'EOF'
---
"@myorg/core":
  bump: minor
  cascade:
    "@myorg/plugin-*": patch
    "@myorg/cli": minor
"@myorg/utils": patch
---

Added new encryption provider. Plugins need a patch bump for compatibility.
EOF

Advanced: omitting an entry from the changelog

If a change needs a version bump but shouldn't appear in the changelog (internal refactor, dependency tidy-up, etc.), add the $changelog: false reserved key. The bump still applies and cascades normally, but this file's body is omitted from the changelog and release notes — write the body anyway as a note for reviewers:

bash
cat > .bumpy/<name>.md << 'EOF'
---
"@myorg/core": patch
$changelog: false
---

Internal refactor of the config loader — no user-facing change.
EOF

It's a file-level flag (a bump file has one shared body), so it applies to every package the file lists.

Important notes

  • Only include packages that have actual code changes — bumpy handles dependency propagation automatically
  • If the user hasn't made any changes yet, ask what they're planning to change
  • If the change doesn't affect any publishable packages (e.g., only root config files), suggest using bumpy add --empty to satisfy CI checks
  • One bump file per logical change — don't combine unrelated changes
  • Keep bump files up to date — as work continues on a branch, the bump file should reflect the final state of all changes, not just the first commit. If packages were added/removed or the bump level changed (e.g., a patch fix grew into a minor feature), update the existing bump file accordingly

© zap-studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/bumpy-add-change of zap-studio/monorepo.

Open the folder on GitHubat commit 8dd89f1

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in zap-studio/monorepo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bumpy Add Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bumpy Add Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bumpy Add Change this skillzap-studio/monorepo1721 repos~1.4kAutomated safety check: NotesMIT
Typescript Expertcin12211/orca-q22412 repos~3.7kAutomated safety check: PassMIT
TypeScript Monorepo Conventionspierrecomputer/pierre6.2k—~450Automated safety check: PassApache-2.0
TypeScript ProJeffallan/claude-skills12k1 repos~1.4kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
Nx Importnrwl/nx29k6 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Typescript Expert

    cin12211/orca-q

    TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.

    224 GitHub starsUsed in 12 repos~3.7k tokens
    DevelopmentAuto-check passed

  • TypeScript Monorepo Conventions

    pierrecomputer/pierre

    Conventions for adding packages and apps to a TypeScript monorepo: project references, moon tasks, workspace dependencies and published package exports.

    6.2k GitHub stars~450 tokensUpdated today
    DevelopmentAuto-check passed

  • TypeScript Pro

    Jeffallan/claude-skills

    Designs advanced TypeScript types: generics, conditional and mapped types, branded types, discriminated unions and type guards, with tsc checks and tRPC type safety.

    12k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 6 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Bumpy Add Change

What does Bumpy Add Change do?

Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation. Bumpy Add Change is an agent skill from zap-studio/monorepo. Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation.

When should I use Bumpy Add Change?

Bumpy Add Change fits situations like: the user wants to record a change; add a bump file; prepare packages for release.

How do I install Bumpy Add Change in Claude Code?

Run `npx skills add zap-studio/monorepo --skill bumpy-add-change -a claude-code`. Or copy the skill folder (.agents/skills/bumpy-add-change in zap-studio/monorepo) into .claude/skills/bumpy-add-change in your project. Claude Code loads it when a task matches its description.

How do I install Bumpy Add Change in Codex?

Run `npx skills add zap-studio/monorepo --skill bumpy-add-change -a codex`. Or copy the skill folder (.agents/skills/bumpy-add-change in zap-studio/monorepo) into .agents/skills/bumpy-add-change in your project. Codex loads it when a task matches its description.

Can I use Bumpy Add Change in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zap-studio/monorepo --skill bumpy-add-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bumpy-add-change, .gemini/skills/bumpy-add-change, .github/skills/bumpy-add-change and .opencode/skills/bumpy-add-change in your project.

What does Bumpy Add Change need to run?

Going by SKILL.md and its folder, Bumpy Add Change needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Edit, Write.

Does Bumpy Add Change access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bumpy Add Change safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Bumpy Add Change use?

Bumpy Add Change is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bumpy Add Change use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bumpy Add Change?

Skills that share tags, products or a category with Bumpy Add Change: Typescript Expert (cin12211/orca-q, 224 stars), TypeScript Monorepo Conventions (pierrecomputer/pierre, 6.2k stars), TypeScript Pro (Jeffallan/claude-skills, 12k stars) and Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bumpy Add Change?

zap-studio (a GitHub organization) maintains it in zap-studio/monorepo, which has 172 GitHub stars. The repository was last updated on October 6, 2026.

Source: zap-studio/monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.