docs-sync Skill
Diff src/ and .github/ against docs/ to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths/modules/diagrams/syntax/agents/skills/hooks), or before a release. Use for questions like "is docs in sync?", "what changed since the last docs update?", " Published by microsoft in learn-ai-native-dev.
What is docs-sync Skill?
Diff src/ and .github/ against docs/ to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths/modules/diagrams/syntax/agents/skills/hooks), or before a release. Use for questions like "is docs in sync?", "what changed since the last docs update?", " Published by microsoft in learn-ai-native-dev. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Documentation
- Data analysis
- Design and media
- Writing
Technical details
- Install or run with Copy skill directory
When to use docs-sync Skill
- Use it for security review.
- Use it for documentation.
- Use it for data analysis.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/learn-ai-native-dev
- Skill file: .github/skills/docs-sync/SKILL.md
What it does
Diff src/ and .github/ against docs/ to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths/modules/diagrams/syntax/agents/skills/hooks), or before a release. Use for questions like "is docs in sync?", "what changed since the last docs update?", "
Skill instructions
Docs Sync (skill) This skill is the diffing playbook the @docs-auditor agent runs. You can also invoke it directly with /docs-sync. It produces a drift report. It does not write to docs/. Apply changes by delegating to @author. Inputs - $ARGUMENTS (optional) — restrict the audit to one of: paths | tracks | components | syntax | harness | routes | lifecycle | links | all. Default: all. Procedure Step 1 — Snapshot the code Collect, in this order: 1. src/data/paths.ts exports. 2. All path.json files under src/content/community//. 3. Frontmatter (id, number, title, subtitle) of every markdown file under src/content/{tutorial,advanced,terminal}/. 4. The list of files under src/components/diagrams/ (excluding index.ts). 5. The list of files under .github/{instructions,prompts,skills,agents,hooks}/. 6. The route table from src/App.tsx. Step 2 — Snapshot the docs Collect: 1. The track tables in docs/tracks/{foundation,agentic,terminal}.md and the contribution-shape table in docs/community-cont
Explore related resources
Frequently asked questions
What is docs-sync?
docs-sync is a open-source AI agent skill with Copy skill directory. Diff src/ and .github/ against docs/ to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding.
Who is docs-sync best for?
docs-sync is best for reusing agent instructions, scripts, and references, security review workflows, documentation workflows, data analysis workflows.
How do I install docs-sync?
Install or run docs-sync using Copy skill directory. Check docs-sync for the latest setup command.
Is docs-sync actively maintained?
docs-sync may need a closer maintenance check before production use.
Auto-fetched from GitHub.
