skill-from-codebase

You can keep documentation in sync by running an automation workflow that derives and validates repository SKILL.md content directly from committed git history, preventing drift between code and documentation. It only regenerates changed sections.

Incremental documentation generation is the process of refreshing only the affected sections of a canonical SKILL.md file. It validates updates against the repository structure and preserves existing unchanged content during safe merges.

Yes, you need a clean git working tree. The generation workflow requires access to git history since the last generated commit and a valid frontmatter-bearing SKILL.md to perform safe, incremental updates without conflicts.

To validate SKILL.md against the repository structure, run the refresh workflow which checks the derived content against committed code changes before writing. This ensures safe merges and prevents invalid documentation updates.

The best way to maintain a canonical SKILL.md is using an automation workflow that enforces incremental updates. It derives content from committed code, validates it, and safely merges only the changed sections while preserving the rest.