Align project documentation with implemented features and code changes.
npx skills add https://github.com/jmylchreest/aide --skill docs-jmylchreest
Please help me install this Agent Skill. Skill: docs Source: https://github.com/jmylchreest/aide/tree/main/skills/docs Command: npx skills add https://github.com/jmylchreest/aide --skill docs-jmylchreest
Documentation often drifts from the actual implementation, leading to user confusion and maintenance overhead. This skill ensures the project docs stay accurate and up-to-date with features, behavior, and configurations.
Update the documentation to reflect the latest implementation.
High-intent search queries and answers about installing and using this skill.
To keep READMEs and API docs aligned with implemented code, apply documentation updates across multiple files and contexts to reflect the latest code changes, tests, and configurations. This solves documentation drift by ensuring project docs accurately match implemented features and behavior.
Preventing documentation drift requires continuously updating architecture documents and inline comments alongside code changes. Ensure modifications reflect the latest tests and configurations while adhering to the SDLC workflow to keep project docs accurate and up-to-date.
Yes, you can update inline comments and architecture documents across multiple files. The process applies changes to reflect the latest implemented features and behavior, ensuring comprehensive coverage across various project contexts.
Yes, the documentation update process supports the end-to-end SDLC workflow. It guides teams to document changes quickly and accurately by ensuring updates reflect the latest code changes, tests, and configurations throughout the software development lifecycle.
Project docs drift from actual implementation when updates do not reflect the latest code changes, tests, and configurations. Solving this requires aligning READMEs, public APIs, and inline comments with the current implemented behavior.
leogodin217Audit code changes for dead code, test naming, and spec drift.
jokken79Generate API references, READMEs, user guides, and architecture diagrams from codebases.
jeremydhoover-blipManage documentation with version control, CI/CD, and automated testing.
windyskyGenerate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.
