make-changelog

What I do

• Create initial CHANGELOG.md file using Keep a Changelog format
• Extract up to 10 major features from README.md, commit history, and codebase structure
• Place all extracted entries under [Unreleased] section (no version number yet)
• Classify entries into Added or Misc based on whether they describe new capabilities or notable catch-all code changes
• Include empty sections for Changed, Deprecated, Removed, Fixed, Security, and Misc at the end
• Note adherence to Semantic Versioning for future releases
• Notify if additional important features exist beyond the top 10
• Provide guidance on moving to versioned releases later

When to use me

Use this skill when:

• Starting changelog documentation for an existing project
• Project has no CHANGELOG.md file yet
• You want to document current state before making first release
• You need a Keep a Changelog compliant starting point

Prerequisites

Required:

• Must be a git repository
• Must have main or master branch

Optional:

• README.md file (used for feature extraction if present)

Validation checks:

# Check if git repo
git rev-parse --git-dir

# Check if CHANGELOG.md already exists
[ -f CHANGELOG.md ]

Error messages:

• Not a git repo → "Error: This skill requires a git repository for context gathering."
• CHANGELOG.md exists → "Error: CHANGELOG.md already exists. This skill is for first-time changelog creation only."
• No main/master branch → "Error: No main or master branch found. Please create a default branch first."

References

This skill follows:

• Keep a Changelog: https://keepachangelog.com/en/1.1.0/
• Semantic Versioning: https://semver.org/spec/v2.0.0.html

If you need to fetch detailed information about changelog format or versioning rules during execution, use the WebFetch tool with these URLs.

Workflow

Step 1: Validate Prerequisites

# Check if git repository
git rev-parse --git-dir 2>/dev/null

If fails → error: "Error: This skill requires a git repository for context gathering."