Sync code changes to living docs, API docs, and changelogs.
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-documentation
Please help me install this Agent Skill. Skill: meow:documentation Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Adocumentation Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-documentation
Documentation often drifts after code changes, slowing onboarding and API adoption. This skill provides a structured workflow to keep living docs, changelogs, and API documentation synchronized with the codebase.
Run the living documentation workflow to update affected docs after code changes.
High-intent search queries and answers about installing and using this skill.
To keep API documentation in sync with code changes, you can automate living-documentation updates that validate diffs before applying changes. This updates API reference docs to match current endpoint implementations while preserving unchanged content.
You can generate a changelog from conventional commits by running a changelog generation integration that appends entries from your commit history. This automates changelog updates alongside your living docs during codebase changes.
Living documentation is a dynamic docs system that stays updated by syncing directly with code changes. It automatically applies updates to reflect recent modifications without rewriting existing content, preventing manual documentation drift.
Yes, this documentation automation preserves your existing markdown content by validating diffs before applying changes. It loads authoritative sources like living-docs.md and api-sync.md, only updating sections affected by recent code modifications.
Yes, you can update living docs without rewriting the entire document by applying diff-aware synchronization. This method targets only the sections impacted by recent code changes, leaving all unchanged content perfectly intact.
You should run the living documentation workflow during the Phase 6 Reflect stage or for explicit doc requests after code changes. This ensures API docs, changelogs, and living docs accurately reflect the current codebase state.
Hexsis-LLCGenerate conventional one-line commit messages from git diffs.
JongsixGenerate technical documentation from source code and API definitions.
AlexandreLabUpdate repository documentation files after merged code changes.
channgGenerate static documentation websites from markdown files with sidebar navigation.
