What documentation standards does this skill follow?

The skill adheres to the 'Keep a Changelog' format and utilizes Semantic Versioning (MAJOR.MINOR.PATCH) for all project updates.

How does the FAILURELOG.md feature help my workflow?

It documents failed attempts, error messages, and root cause analyses during complex tasks, preventing you from repeating the same mistakes and preserving institutional knowledge.

When should I activate the changelog skill?

You should trigger it whenever you make code changes, add features, fix bugs, restructure files, or when an initial solution fails and requires documented debugging.

Which specific files are managed by this skill?

It manages three primary files: CHANGELOG.md for change tracking, FILETREE.md for directory structure, and FAILURELOG.md for recording debugging history.

Changelog & Documentation Manager

Name: Changelog & Documentation Manager
Author: robin-collins

byrobin-collins

Content Management

Maintains standardized project documentation including changelogs, file trees, and debugging history using industry-standard formats.

About

This skill provides a systematic approach to project documentation within Claude Code by automating the maintenance of CHANGELOG.md, FILETREE.md, and FAILURELOG.md. By enforcing the 'Keep a Changelog' format and Semantic Versioning, it ensures that every code modification, structural reorganization, and debugging insight is recorded accurately. This tool is essential for developers who want to maintain high-quality project history, improve institutional knowledge, and streamline the release process through consistent documentation of features, fixes, and architectural changes.

Key Features

Automated FILETREE.md synchronization for structural directory changes
Detailed FAILURELOG.md tracking to document debugging attempts and root causes
Semantic Versioning (SemVer) management for consistent release numbering
Categorized entry management (Added, Changed, Fixed, Security, etc.)
0 GitHub stars
Standardized CHANGELOG.md updates following 'Keep a Changelog' guidelines

Use Cases

Maintaining a professional release history for open-source repositories
Documenting complex debugging sessions to prevent repetitive troubleshooting cycles
Synchronizing project directory documentation during large-scale refactoring

About

Key Features

Automated FILETREE.md synchronization for structural directory changes
Detailed FAILURELOG.md tracking to document debugging attempts and root causes
Semantic Versioning (SemVer) management for consistent release numbering
Categorized entry management (Added, Changed, Fixed, Security, etc.)
0 GitHub stars
Standardized CHANGELOG.md updates following 'Keep a Changelog' guidelines

Use Cases

Maintaining a professional release history for open-source repositories
Documenting complex debugging sessions to prevent repetitive troubleshooting cycles
Synchronizing project directory documentation during large-scale refactoring