Documentation synchronization knowledge. Use when analyzing documentation patterns, understanding how code changes map to documentation needs, or determining documentation structure for different project types.
From doc-syncnpx claudepluginhub lifegenieai/lifegenie-claude-marketplace --plugin doc-syncThis skill is limited to using the following tools:
references/change-mapping.mdreferences/doc-patterns.mdFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
Knowledge base for documentation synchronization, covering patterns for different project types and how code changes typically map to documentation needs.
Good documentation:
Documentation drift happens when:
Different types of code changes require different documentation updates:
| Code Change | Documentation Need |
|---|---|
| New feature | Feature doc, routes, API reference |
| Architectural decision | ADR (Architecture Decision Record) |
| New dependency | Tech stack reference |
| Config change | Guides, deployment docs |
| Schema change | Data model docs |
For detailed patterns and mappings, see:
references/doc-patterns.md - Documentation patterns by project typereferences/change-mapping.md - How code changes map to doc typesThis skill supports the /update-docs command and its agents:
git-change-analyzer - Uses change mappingsdoc-gap-analyzer - Uses doc patternsdoc-updater - Uses both for context