What documentation formats does this skill support?

The skill strictly follows the 'Keep a Changelog' standard and uses Semantic Versioning (MAJOR.MINOR.PATCH) with YYYY-MM-DD date formatting for all entries.

When should I trigger the changelog skill?

You should trigger this skill whenever you make code changes, add features, fix bugs, or restructure your project's directory to ensure documentation remains in sync with the code.

Why is a FAILURELOG.md necessary?

It serves as a historical record of failed debugging attempts, including error messages and root cause analysis, which prevents repeating the same debugging cycles.

How does it handle version increments?

It applies SemVer logic by incrementing the MAJOR version for breaking changes, MINOR for new features, and PATCH for bug fixes.

Changelog & Documentation Manager

Name: Changelog & Documentation Manager
Author: robin-collins

byrobin-collins

Learning & Documentation

Maintains standardized project documentation including changelogs, file trees, and debugging logs to ensure consistent project tracking and semantic versioning.

About

The Changelog & Documentation Manager is a specialized skill for Claude Code designed to automate and standardize project record-keeping. It provides systematic guidance for maintaining three essential files: CHANGELOG.md for feature and bug tracking, FILETREE.md for structural visibility, and FAILURELOG.md for capturing debugging insights. By enforcing industry standards like 'Keep a Changelog' and Semantic Versioning, it helps developers maintain a transparent history of project evolution, improves collaboration through clear documentation, and prevents the loss of institutional knowledge during complex debugging sessions.

Key Features

Standardized CHANGELOG.md updates using 'Keep a Changelog' format
Automated FILETREE.md maintenance for project structure visibility
Context-aware grouping of changes into standard categories like Added, Fixed, and Security
0 GitHub stars
FAILURELOG.md documentation to track debugging attempts and root causes
Strict enforcement of Semantic Versioning (SemVer) principles

Use Cases

Automating release notes and versioning during deployment cycles
Maintaining an up-to-date visual map of the project directory structure for large repositories
Documenting complex debugging sessions to prevent repetitive failures and capture root causes

About

Key Features

Standardized CHANGELOG.md updates using 'Keep a Changelog' format
Automated FILETREE.md maintenance for project structure visibility
Context-aware grouping of changes into standard categories like Added, Fixed, and Security
0 GitHub stars
FAILURELOG.md documentation to track debugging attempts and root causes
Strict enforcement of Semantic Versioning (SemVer) principles

Use Cases

Automating release notes and versioning during deployment cycles
Maintaining an up-to-date visual map of the project directory structure for large repositories
Documenting complex debugging sessions to prevent repetitive failures and capture root causes