// Generate a changelog for npm releases by analyzing git commits and categorizing changes
| name | cli:create-changelog |
| description | Generate a changelog for npm releases by analyzing git commits and categorizing changes |
| disable-model-invocation | true |
| allowed-tools | Bash(git:*), Read, Write |
| argument-hint | [since-tag] |
Generate a clear, human-readable changelog for this CLI project to publish with new npm releases.
When this skill is invoked:
git fetch --tags to ensure local tags are up to date with the remotegit tag --sort=-version:refname to identify the latest tag matching format vX.Y.Z (e.g., v7.11.2)/create-changelog v7.10.0), use that tag insteadgit log <tag>..HEAD --format="%h|%s|%an|%ad" --date=short --no-merges to get commit detailsReview each commit and categorize into groups (in order of severity):
Apply semantic versioning rules (https://semver.org/):
Provide clear reasoning for your recommendation.
Use the template below and fill all sections with concise bullet points. Write in clear, user-friendly language.
After generating the changelog:
CHANGELOG_<version>.md in the repository rootCHANGELOG_8.0.0.md# Release X.Y.Z [Major|Minor|Patch]
Full commit diff can be found [HERE](https://github.com/HubSpot/hubspot-cli/compare/vX.Y.Z...main)
## Reasoning
_Explain concisely (2–4 sentences) why this release is [major/minor/patch], referencing the change scope and user impact._
## To be announced
- _Key user-facing announcements (major changes, restructuring, or deprecations)._
## Notable changes
### Breaking Changes
- _Detail any backward-incompatible changes or mandatory migrations._
### New Features
- _Summarize new commands, options, or major user-facing features._
### Bug Fixes
- _Describe what was fixed and the improvement for users._
### Improvements and Refactoring
- _Detail performance, code quality, or internal changes visible to maintainers or advanced users._
Review code changes in current branch for adherence to team guidelines and conventions
Design and refine HubSpot CLI commands, copy, and interaction patterns against established design guidelines and industry best practices (clig.dev, Heroku, Atlassian, HotCoA). Use when an engineer needs help with CLI design decisions — command/flag/arg structure, error messages, help text, prompts, success messages, warnings, progress output, configuration conventions, environment variables, interactivity patterns, naming, or accessibility. Trigger on "help me design this command", "review this CLI text", "write an error message for", "what should this prompt say", "how should I structure these flags", or any request about HubSpot CLI design, wording, tone, or behavior.