Changelog Scribe
Automates changelog generation, SemVer recommendations, and release audits from git history and PR metadata.
$25
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsChangelog Scribe
Example session with this skill installed
Write a changelog for the changes since v1.2.0. Check the merged PRs and verify if we need a minor or major bump. Update CHANGELOG.md.
- Read your context and instructions
- Compiled the changelog scribe
I have analyzed the 14 commits and 3 merged PRs since tag v1.2.0. I found one breaking change in the CLI argument parser and two new features.
Release Draft: v2.0.0
Semver Recommendation: MAJOR bump (v1.2.0 -> v2.0.0)
Reason: PR #42 ("Refactor CLI flags") removed the --legacy-auth flag, which is a breaking change for CI workflows.
Developer Changelog (CHANGELOG.md)
## [2.0.0] - 2023-10-24
### Added
- Export `ValidationSchema` type for external middleware support (#45)
- Support for YAML configuration files via `config.yaml` (#43)
### Changed
- [BREAKING] Refactor CLI argument parsing. The `--legacy-auth` flag has been removed. (#42)
### Fixed
- Memory leak in the connection pooler during high concurrency (#44)
Customer-Facing Release Notes
New Features & Improvements
YAML Configuration: You can now manage your settings using YAML files, making complex configurations easier to read.
- Performance Fixes: Resolved a stability issue that caused high memory usage under heavy load.
Breaking Changes
- The old
--legacy-authcommand-line option has been retired. Please update your deployment scripts to use the new authentication flow.
Reviewer Report (GAPs & REVIEWS)
- REVIEW:
package.jsonversion is still1.2.0. It must be updated to2.0.0to match this release.
GAP: Commit f8a2b1 ("update utils") touches public helpers but lacks a description. I have excluded it from the draft.
- REVIEW: PR #42 indicates a breaking change but is missing a specific "Migration Guide" section in the PR body.
Next steps
- Update the version string in
package.jsonto2.0.0. - Provide a brief migration snippet for the removed
--legacy-authflag. - Run
scripts/write_changelog.pyto commit these changes to CHANGELOG.md.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Developers often spend the hour before a release manually hunting through a week of merged PRs to reconstruct a changelog. This process is prone to missing breaking changes, skipping migration notes, and creating version mismatches in manifest files.
What it does
- Analyzes git history, PR metadata, and diffs to extract actual code changes.
- Generates dual-audience notes: a technical CHANGELOG.md entry for devs and a benefit-driven summary for customers.
- Recommends a SemVer bump (Major/Minor/Patch) based on the presence of breaking changes and new features.
- Identifies gaps like undocumented public API changes or missing migration instructions.
- Scans package manifests and docs to flag version string mismatches before you tag the release.
Frameworks & tools
Works with Git, GitHub CLI (gh), and any project using standard version manifests like package.json, pyproject.toml, or Cargo.toml.
Why this beats prompting it yourself
Generic LLM prompts often hallucinate change impacts or invent feature descriptions when the commit message is vague. This skill follows a strict protocol to flag unknowns as GAPs for human review rather than guessing, ensuring your release notes are technically accurate.
Use cases
- Drafting standardized CHANGELOG.md entries from squash-merged PRs.
- Preparing customer-facing "What's New" release emails from technical diffs.
- Verifying SemVer compliance for library releases and monorepo packages.
- Auditing repository files for version string consistency before deployment.
Known limitations
Requires read access to git logs or PR JSON exports. It does not verify the functional safety of code changes or publish directly to external release management platforms.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 1 month ago
- Passed all security checks, Safe to install
Requires
Python