changelog

To generate changelogs from git history, the Skill analyzes repository commits and compiles them into tailored release notes for different audiences. It outputs detailed reports in Markdown or JSON formats.

Documentation auditing compares your project's README against the actual codebase to find outdated instructions, non-existent commands, or API usage errors. It flags these discrepancies and attempts to auto-fix unambiguous inconsistencies.

Yes, you can auto-fix documentation drift because the code audit attempts to automatically correct unambiguous inconsistencies found during the documentation review. It addresses issues in installation, API usage, configuration, and architecture.

No dependencies are required to run a documentation audit for release notes. The Skill operates independently without external dependencies to generate changelogs and check documentation consistency against your codebase.

The best way to keep README files consistent with code changes is to run a documentation audit before each release. This compares documentation against the actual codebase to catch drift and auto-fix unambiguous discrepancies.

Markdown and JSON formats are supported for exporting git changelog and audit reports. The Skill provides detailed consistency reports in these formats to help document installation steps, API usage, configuration, and architecture.