Changelog
Skill Verified ActiveGenerate a changelog from git history since a tag, date, or commit
To automate the creation of changelogs from git history, streamlining release notes generation and improving project documentation.
Features
- Generate changelog from git history
- Supports specifying start point by tag, date, or commit
- Categorizes commits by conventional commit prefixes
- Formats output into a readable changelog structure
- Analyzes commit messages by intent if conventional prefixes are absent
Use Cases
- Creating release notes for software projects
- Documenting changes between versions
- Maintaining a clear history of features and bug fixes
- Automating the changelog generation process
Non-Goals
- Generating changelogs for non-git repositories
- Analyzing commit messages outside of a specified git history range
- Creating changelogs for complex merge commit structures
Workflow
- Parse arguments (since point, repo path)
- Read git log since the specified point
- Categorize commits by conventional commit prefixes (feat, fix, docs, perf, refactor, other)
- Analyze commit messages by intent if no conventional commits found
- Format output into a structured changelog
Installation
npx skills add faizkhairi/claude-code-blueprintRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedTrust Signals
Similar Extensions
Release Manager
100Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.
Changelog From Commits
99Generate a user-facing CHANGELOG entry from raw git log output. Use when the user is preparing a release, says "what changed since last version", asks to write release notes, or wants to summarize a batch of commits for end users.
Create Github Release
98Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or distributing build artifacts (binaries, tarballs).
Manage Changelog
97Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.
Release Skills
95Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".
OpenClaw Release Maintainer
100Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.