What problem does it solve? In repositories managed by changepacks, a pull request that changes a tracked package must include a changepack log, or the version never bumps and the change ships without ever being released. This Skill ensures agents add the correct log file non-interactively instead of hanging on the tool's interactive prompt. ## Core Features & Use Cases - Non-interactive log creation: Runs changepacks with --yes, --update-type, and --message flags so it works in agent shells and CI where the interactive UI would hang. - Config-driven scope detection: Reads .changepacks/config.json ignore patterns to decide whether a change actually requires a changepack. - Bump level guidance: Maps changes to major, minor, or patch based on consumer impact. - CI failure recovery: Explains how to fix a failing "changepack required" check by adding and committing the log. - Use Case: Before opening a PR that modifies crates/my-crate/Cargo.toml, run bunx @changepacks/cli -y -u patch -m "why this changed" and commit the generated .changepacks/changepack_log_<name>.json. ## Quick Start Check whether this repository has a .changepacks directory and, if my changes touch a tracked package, create a patch changepack log with a message explaining what changed.
