audit-changelog

Verify CHANGELOG.md format and content against Git history.

4|Updated Aug 14, 2025

Search Tags:#git #changelog #audit #manual #release preparation

Ready to run

npx skills add https://github.com/ironsheep/P2-Knowledge-Base --skill audit-changelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-changelog
Source: https://github.com/ironsheep/P2-Knowledge-Base/tree/main/.claude/skills/audit-changelog
Command: npx skills add https://github.com/ironsheep/P2-Knowledge-Base --skill audit-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of a P2 manual's CHANGELOG.md for release readiness, ensuring that its voice/structure conforms to guidelines and claims align with actual commits.

Core Features & Use Cases

Audit CHANGELOGs: Automatically check changelogs for correct format and content alignment.
Release Preparation: Identify any issues that would prevent a smooth release.
Use Case: When preparing to release a new version of a P2 manual, use this Skill to ensure the CHANGELOG is accurate and complete.

Quick Start

Use the /audit-changelog command followed by the manual slug (e.g., /audit-changelog p2-pasm-desilva-style) to verify the changelog.

Frequently Asked Questions about audit-changelog

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

FAQPage Schema

How do I audit a changelog against actual Git history?▼

To audit a changelog against Git history, this Skill verifies your CHANGELOG.md by cross-referencing its entries with actual repository commits and checking structure against a predefined style guide.

Can I verify changelog format and content alignment before a release?▼

Yes, you can verify changelog format and content alignment before a release by running an automated audit that identifies structural issues and checks if claims match actual Git commits.

How do I check if a P2 manual's CHANGELOG.md is release-ready?▼

You can check if a P2 manual's CHANGELOG.md is release-ready by executing the audit command with the manual slug to automatically validate its voice, structure, and commit alignment.

Do I need Git installed to verify repository history for changelog audits?▼

Yes, you need Git installed and accessible in your environment, because this Skill requires direct access to repository history to validate that changelog claims match actual commits.

What is the best way to ensure changelog accuracy for release preparation?▼

The best way to ensure changelog accuracy for release preparation is to automate the verification process, cross-checking manual changelog entries against predefined style guidelines and actual Git commit history.

Why does my changelog audit fail during manual release preparation?▼

A changelog audit may fail during release preparation if the CHANGELOG.md voice or structure deviates from style guidelines, or if documented changes do not align with actual Git commit history.