Detect documentation drift from git history and propose edits to project docs.
npx skills add https://github.com/t6adev/claude-code-tools --skill doc-sync-t6adev
Please help me install this Agent Skill. Skill: doc-sync Source: https://github.com/t6adev/claude-code-tools/tree/main/tools/skills/docs/doc-sync Command: npx skills add https://github.com/t6adev/claude-code-tools --skill doc-sync-t6adev
This skill automates the process of reconciling documentation with code changes by reading git history, identifying drift between CLAUDE.md, docs/architecture.md, docs/requirements.md, and README.md, and proposing targeted updates that are applied only after user approval.
Ask doc-sync to read git diff and propose targeted doc updates.
High-intent search queries and answers about installing and using this skill.
To keep documentation in sync, doc-sync reads recent git history to detect documentation drift and proposes targeted edits to CLAUDE.md, docs/architecture.md, docs/requirements.md, and README.md. Updates are applied only after user approval.
Documentation drift occurs when project docs become outdated relative to code changes. You can detect documentation drift by reading git history to identify inconsistencies between your current code and files like CLAUDE.md, docs/architecture.md, and README.md.
To update CLAUDE.md and README.md based on git history, you can use a documentation-sync workflow that reads recent commits, identifies drift, and proposes focused edits. The proposed changes are then applied stepwise only after human confirmation.
No, documentation updates to docs/architecture.md cannot be applied automatically without manual review. The change-propagation workflow ensures controlled, minimal changes by applying proposed edits only after explicit user approval.
No, doc-sync focuses on reconciling documentation drift specifically within CLAUDE.md, docs/architecture.md, docs/requirements.md, and README.md. It proposes minimal edits to these targeted files rather than supporting arbitrary documentation paths.
The best way to propagate code changes to project documentation is using an automated review-and-apply workflow. It reads git history, identifies drift across CLAUDE.md and docs files, and proposes focused edits that are applied only after user approval for controlled synchronization.
ligianehuaUpdate project documentation files based on the repository diff.
Eigo-Mt-FujiAutomate CI/CD pipelines and infrastructure across Docker, Kubernetes, and Terraform.
severity1Update AUTO-MANAGED sections in CLAUDE.md files after code changes.
ogprotegeAudit repository documentation against code and recent changes.
