Align repository documentation with code evidence using minimal patches.
npx skills add https://github.com/johnqtcg/awesome-skills --skill update-doc-johnqtcg
Please help me install this Agent Skill. Skill: update-doc Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/update-doc Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill update-doc-johnqtcg
Keeps repository documentation synchronized with the latest code evidence, ensuring docs stay accurate and reducing stale information across README s, CODEMAPS, and developer guides.
Run the doc-drift workflow to align project documentation with code changes.
High-intent search queries and answers about installing and using this skill.
To keep documentation in sync with code changes across a monorepo, you can run an automated doc-drift workflow that uses repository files as the single source of truth and generates minimal, diff-scoped patches for your READMEs and CODEMAPS.
Docs-drift is the gap between your current codebase and your repository documentation. You detect it by running a workflow that surfaces evidence-backed updates, comparing repository files against existing docs and marking any missing information as Not found in repo.
You update README files automatically by applying a workflow that enforces repository files as the truth and outputs minimal patches to align the documentation with new code behavior while preserving the existing structure of the files.
Yes, you can prevent stale documentation by generating diff-scoped patches that minimize changes, applying only the necessary edits required to align your docs with specific code updates rather than rewriting entire files.
Yes, the update process explicitly preserves the existing structure of your documentation by outputting minimal patches that align the content with the codebase without unnecessarily altering the original formatting.
kettleofketchupAnalyze git diffs to identify required MkDocs documentation changes.
kent013Audit and update Alpha Factory documentation against source code and config defaults.
adolfoaranaes12Validate architecture.md documents against a checklist and produce structured reports.
mvallimGenerate Markdown documentation from codebases with customizable headings and dependencies.
