changelog

Generate structured changelogs from git commits, sprint reports, and design documents.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill changelog-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill changelog-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of compiling release notes by automatically extracting relevant changes from git history, sprint reports, and design documents, producing both detailed internal logs and concise player‑facing summaries.

Core Features & Use Cases

  • Git Integration: Pulls recent commits and tags to determine change scope.
  • Sprint & Design Data: Reads sprint reports and GDD files to enrich the changelog with context.
  • Dual Output: Generates a comprehensive internal changelog and a polished player‑facing version ready for publishing.
  • File Management: Optionally writes the result to docs/CHANGELOG.md, handling append or overwrite logic.

Quick Start

Run the changelog skill with the desired version or sprint number to receive both internal and player-friendly changelog documents.

Frequently Asked Questions about changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate a changelog from git commits and sprint reports?

You can auto-generate a changelog from git commits and sprint reports by using a tool that reads repository files, executes the git CLI, and writes a structured markdown output combining internal logs and player-facing summaries.

What is the best way to create player-facing release notes from git tags and design documents?

The best way to create player-facing release notes from git tags and design documents is to extract relevant changes from versioned git history and GDD files, producing a polished summary ready for publishing.

Does the changelog automation tool require read access to my repository files?

Yes, changelog automation requires read access to your repository files and git CLI execution permission to pull recent commits, read sprint folders, and access GDD files for context.

Can I automatically write the generated changelog to a markdown file in my docs folder?

Yes, you can automatically write the generated changelog to `docs/CHANGELOG.md`, with the tool handling append or overwrite logic to manage your file updates.

How does a dual-output changelog generator work for software projects?

A dual-output changelog generator works by extracting changes from git history, sprint reports, and design documents to produce both a comprehensive internal changelog and a concise player-facing version.