Detect and fix drift between code and TECH_SPEC_current.md documentation.
npx skills add https://github.com/lshtram/core_dev --skill doc-maintainer-lshtram
Please help me install this Agent Skill. Skill: doc-maintainer Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/doc-maintainer Command: npx skills add https://github.com/lshtram/core_dev --skill doc-maintainer-lshtram
Documentation often drifts from the actual code; this skill ensures living documentation stays in sync by reverse-syncing code to docs.
Drift detection: identify where docs diverge from code.
Sync actions: update TECH_SPEC_current.md to match actual implementation; update guidelines if new patterns emerge; archive old specs to .agent/archive.
Use Case: Example involving multiple microservices and evolving APIs; maintain consistent docs with code.
Run a doc-sync to compare implementation with TECH_SPEC_current.md and apply updates.
High-intent search queries and answers about installing and using this skill.
Documentation drift is detected by running a diff analysis that compares actual code implementations against existing TECH_SPEC_current.md files to identify divergences. The skill then applies sync actions to update the tech specs and match the current implementation.
To keep living docs in sync after implementation, run a doc-sync process that reverse-syncs code to documentation. This updates TECH_SPEC_current.md with actual implementation details and archives outdated documents to .agent/archive.
Maintaining accurate tech specs across evolving microservices requires ongoing documentation refreshes using drift detection. The skill handles diff analysis for codebases using TECH_SPEC_current.md, updating guidelines when new API patterns emerge.
Archiving outdated technical specifications works by moving superseded documents to the .agent/archive directory during the documentation refresh process. This ensures living docs remain current while preserving historical tech spec versions.
Yes, you can update documentation guidelines when new code patterns emerge as part of the sync actions. The skill identifies drift during diff analysis and applies updates to both TECH_SPEC_current.md and guidelines to reflect new implementation patterns.
Yes, code-to-docs reverse syncing requires codebases that use TECH_SPEC_current.md files. The skill performs diff analysis specifically against this file format to detect drift and apply documentation updates.
githubConfigure GitHub Copilot custom agent files under .github/agents with Markdown frontmatter.
JSai23Generate production code, tests, and living documentation from milestone plans.
greencmMerge pull requests, run CI tests, and deploy to production with canary checks.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
