Consolidate scattered documentation into standardized module READMEs and CHANGELOGs.
npx skills add https://github.com/ayanjiushishuai/dev_toolkits --skill doc-integrate
Please help me install this Agent Skill. Skill: doc_integrate Source: https://github.com/ayanjiushishuai/dev_toolkits/tree/main/skills/doc_integrate Command: npx skills add https://github.com/ayanjiushishuai/dev_toolkits --skill doc-integrate
Scattered documentation across a codebase is hard to maintain and prone to drift; this Skill consolidates disparate docs into standardized module paths and ensures alignment with code.
Run /doc_integrate to start the documentation consolidation workflow.
High-intent search queries and answers about installing and using this skill.
To consolidate scattered documentation, this Skill scans fragmented files, merges them into standardized .dev_doc/<module>/ READMEs, validates content against current code, and updates a unified CHANGELOG.
Aligning code with documentation is best handled by using code as the source of truth and verifying changes through git history to enforce accuracy between implementations and module READMEs.
Git history helps validate documentation drift by tracking code changes over time, allowing the consolidation process to verify that module READMEs accurately reflect the current implementation state.
Yes, you can update a unified CHANGELOG while merging scattered docs. The workflow consolidates design and plan notes into module READMEs and aggregates changelog entries simultaneously.
No external dependencies are required. The workflow operates independently to scan codebases with fragmented docs, validate against implementations, and merge content into standardized module paths.
o2b3kGenerate a landing-page README and cross-linked documentation directory from scattered markdown files.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.
kvetAnalyze git changes to detect documentation drift and generate a findings report.
tomique34Generate Markdown API documentation from OpenAPI specs, Python docstrings, and JSDoc/TSDoc comments.
