Changelog Scribe

    1

    Automates changelog generation, SemVer recommendations, and release audits from git history and PR metadata.

    $25

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Changelog 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
    • Generated the document

    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-auth command-line option has been retired. Please update your deployment scripts to use the new authentication flow.

    Reviewer Report (GAPs & REVIEWS)

    • REVIEW: package.json version is still 1.2.0. It must be updated to 2.0.0 to 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

    1. Update the version string in package.json to 2.0.0.
    2. Provide a brief migration snippet for the removed --legacy-auth flag.
    3. Run scripts/write_changelog.py to commit these changes to CHANGELOG.md.

    changelog-scribe.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Generate categorized CHANGELOG.md entries from git logs and PR descriptions.Draft non-technical release notes for customers and stakeholders.Recommend Major/Minor/Patch version bumps based on code impact analysis.Identify missing migration notes or undocumented public API changes.Validate version string consistency across multiple manifest files.

    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 install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    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

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 5 days ago

    • Passed all security checks, Safe to install

    Listed5 days ago

    Frequently Asked Questions