dev-changelog

Name: dev-changelog
Availability: InStock
Author: CodiHaus

Generate changelog documents mapping code changes to specs and use cases.

Updated Jan 25, 2026

Search Tags:#changelog #documentation #handoff #sprint #developer #release-notes #user-impact

Ready to run

npx skills add https://github.com/codihaus/claude-skills --skill dev-changelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-changelog
Source: https://github.com/codihaus/claude-skills/tree/main/skills/dev-changelog
Command: npx skills add https://github.com/codihaus/claude-skills --skill dev-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracking and communicating what changed during development is error-prone without a structured process. A dedicated dev-changelog captures both developer progress and user-facing impact, ensuring clear handoffs and release notes.

Core Features & Use Cases

Generate a concise developer summary of changes, mapped to specs and use cases.
Produce user-impact notes for release notes and guides.
Provide outputs: summary.md, user-impact.md, implementation.md, tech-debt.md, docs-updates.md, with links to commits, PRs, specs, and use cases.
Supports resuming work later by creating a persistent, traceable trail of what was done and what remains.

Quick Start

Run the /dev-changelog command after a dev-review passes to generate the documentation pack.

Frequently Asked Questions about dev-changelog

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

FAQPage Schema

How do I generate developer release notes and changelogs after a sprint code review?▼

Generate developer release notes and changelogs by collecting implemented changes after code review and mapping them to specs and use cases, producing summary.md, user-impact.md, and implementation.md for clear sprint handoffs.

What is the best way to document user-impact and tech-debt for software handoffs?▼

Document user-impact and tech-debt for software handoffs by tying git commits and PRs to specs, generating dedicated user-impact.md and tech-debt.md files that provide traceability and clear stakeholder notes.

Can I trace git commits and PRs back to original specs and use cases?▼

Yes, you can trace git commits and PRs back to original specs and use cases by mapping implemented changes during changelog generation, creating a persistent trail of what was done and what remains.

Does this changelog generation process work for end-of-sprint reviews and release cycles?▼

Yes, changelog generation works for end-of-sprint reviews and release cycles by summarizing implemented changes and generating docs-updates.md and implementation.md outputs for stakeholder communication.

What specific markdown files are produced when documenting post-review code changes?▼

Documenting post-review code changes produces summary.md, user-impact.md, implementation.md, tech-debt.md, and docs-updates.md, all linked to git commits and PRs for traceability.