Check a documentation file for drift against the actual codebase — CLI commands, file paths, config keys, function signatures, version numbers, environment variables — and propose corrections. Use when the user wants to audit README.md, docs/*.md, or similar for claims that no longer match reality. Drift usually comes from refactors that forgot to update the docs.
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/docsync?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Escrita e Conteúdo skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Docsync
Compare documentation against the code it describes. Find where the docs say one thing and the code says another. Propose fixes grounded in current code, not in what the docs should have said.
Repo context
/techne:docsync audits a doc that may live in a different repo than your CWD (e.g. /techne:docsync ../velocity-fl/README.md). Skill-context must therefore come from the target's repo, not CWD. A load-time !`cat .claude/skill-context.md` injection can't do this
[Description truncada. Veja o README completo no GitHub.]
