changelog-management

Update CHANGELOG.md, FILETREE.md, and FAILURELOG.md with Keep a Changelog formatting.

Updated Nov 15, 2025

Search Tags:#changelog #documentation #semantic-versioning #change-tracking #filetree #failurelog

Ready to run

npx skills add https://github.com/robin-collins/claude_code_skills --skill changelog-management-robin-collins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-management
Source: https://github.com/robin-collins/claude_code_skills/tree/main/changelog
Command: npx skills add https://github.com/robin-collins/claude_code_skills --skill changelog-management-robin-collins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and updates the three mandatory project documentation files CHANGELOG.md, FILETREE.md, and FAILURELOG.md to reflect code changes, structure updates, and debugging efforts.

Core Features & Use Cases

Automates consistent documentation updates for code changes, feature additions, and bug fixes.
Tracks structural changes via FILETREE.md and records debugging efforts in FAILURELOG.md.
Enforces Keep a Changelog formatting and semantic versioning for release notes.

Quick Start

Document your change by updating the changelog, refresh the file tree map, and log any debugging attempts.

Frequently Asked Questions about changelog-management

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

FAQPage Schema

How do I maintain a changelog using semantic versioning for software releases?▼

You maintain a changelog using semantic versioning by updating CHANGELOG.md to reflect code changes, feature additions, and bug fixes. This approach enforces the Keep a Changelog format, providing consistent structure for release notes during software development.

What is the best way to track project structure updates alongside code changes?▼

The best way to track project structure updates is by maintaining a FILETREE.md file alongside your changelog. This maps structural changes during refactors or feature additions, keeping your file tree documentation synchronized with your actual codebase updates.

How do I document debugging efforts and failure history in a software project?▼

You document debugging efforts by recording them in a FAILURELOG.md file. This creates a consistent placement for logging debugging attempts and failure history during bug fixes or debugging sessions, separating troubleshooting records from standard code changes.

Does this changelog management approach work for both refactoring and feature additions?▼

Yes, this changelog management approach works across software projects during both feature additions and refactors. It provides a consistent format for documenting changes in CHANGELOG.md, structural updates in FILETREE.md, and debugging efforts in FAILURELOG.md.

What format should I use for writing project changelogs and release notes?▼

You should use the Keep a Changelog format with semantic versioning for writing project changelogs and release notes. This standardizes how changes are categorized and documented, ensuring clarity and consistency across all your project documentation updates.