// Manage project changelogs following the Keep a Changelog format. This skill should be used when working with CHANGELOG.md files, adding changelog entries, releasing versions, or reviewing git commits for changelog purposes.
This skill should be used when working with Restate durable execution framework, building workflows, virtual objects, or services that need automatic retries, state management, and fault tolerance. Use when the user mentions "restate", "durable execution", "durable workflows", needs to build resilient distributed systems, or when they invoke /restate.
Distill rough ideas into structured project specs with issues. This skill takes unstructured input (bullet points, rough notes, transcribed ideas) and systematically breaks it down into feature domains, identifies ambiguities requiring user clarification, and produces a single structured spec document with actionable issues. Use this skill when the user wants to transform rough project ideas into well-defined specifications and issues, or when they invoke /speccer.
Jujutsu (jj) workflow skill. This skill should be used when the project uses jj for version control instead of git. Provides guidance on using jj commands and references the jj-vcs skill for detailed documentation.
Jujutsu (jj) version control workflows and commands. Use this skill when working with jj repositories, managing changes, squashing commits, rebasing, or performing jj-specific operations.
Apple's native container runtime for macOS. Use this skill instead of Docker when running on macOS with Apple silicon. The `container` CLI provides OCI-compatible container management optimized for Apple silicon.
Read and write semantic versions in config files (JSON, TOML, YAML). This skill should be used when bumping versions in package.json, Cargo.toml, deno.json, or other config files, or when reading version values from these files.
| name | changelog |
| description | Manage project changelogs following the Keep a Changelog format. This skill should be used when working with CHANGELOG.md files, adding changelog entries, releasing versions, or reviewing git commits for changelog purposes. |
A command line tool for managing changelogs following the Keep a Changelog format.
To add a changelog entry, use the changelog add command:
changelog add --type <TYPE> <DESCRIPTION>
Change types:
added (alias: a) - New featureschanged (alias: c) - Changes in existing functionalitydeprecated (alias: d) - Soon-to-be removed featuresremoved (alias: r) - Removed featuresfixed (alias: f) - Bug fixessecurity (alias: s) - Security fixesEntry Style Guide:
Voice & Tense:
Formatting:
Examples:
changelog add --type added "commands now accept multiple arguments"
changelog add --type fixed "login bug that prevented oauth flow"
changelog add --type changed "error messages now include more context"
changelog add --type removed "deprecated v1 api endpoints have been removed"
To add an entry to a specific version instead of Unreleased:
changelog add --type fixed --version 1.0.1 "critical security patch"
To release the Unreleased section as a new version:
# Automatic semver increment
changelog release major # 1.0.0 -> 2.0.0
changelog release minor # 1.0.0 -> 1.1.0
changelog release patch # 1.0.0 -> 1.0.1
# Explicit version
changelog release 1.0.0
# With custom date
changelog release 1.0.0 --date 2025-01-01
To interactively review git commits and add them to the changelog:
changelog review
This opens an interactive selection interface similar to git rebase -i.
Commits with conventional commit prefixes (feat:, fix:) are pre-selected.
After selection, an editor opens to categorize and reword entries.
# Get latest version
changelog version latest
# List all versions
changelog version list
# Get git revision range for a version
changelog version range 1.0.0
# Show a specific version's entries
changelog entry 1.0.0
changelog entry latest
changelog entry unreleased
# Format the changelog file
changelog fmt
# Initialize a new changelog
changelog init
# Generate shell completions
changelog completions bash
changelog completions zsh
changelog completions fish
Do not manually edit CHANGELOG.md when the changelog CLI is available. Use
changelog add to add entries programmatically, ensuring proper formatting and
structure.