plugins/development/skills/update-documents/SKILL.md
Synchronizes documentation between CLAUDE.md, README.md, and docs/. Resolves documentation inconsistencies across project files with configurable sync rules and whitespace-tolerant comparison.
npx skillsauth add talent-factory/claude-plugins update-documentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically synchronize project documentation between the various documentation files.
| Source | Section | Targets | |--------|---------|---------| | CLAUDE.md | Tech Stack | README.md, docs/index.md | | CLAUDE.md | Development Commands | README.md, docs/development/local-setup.md | | CLAUDE.md | Project Structure | README.md | | README.md | Quick Start | docs/getting-started/quickstart.md |
Principle: CLAUDE.md is the technical source of truth; README.md is the user-facing entry document.
First check the current sync status:
cd ${PROJECT_ROOT} && python ${SKILL_DIR}/scripts/main.py --analyze
The script displays:
If differences were found:
cd ${PROJECT_ROOT} && python ${SKILL_DIR}/scripts/main.py --sync
After synchronization:
Provide the user with a brief summary:
Documentation synchronized
Updated:
- README.md: Tech Stack, Development
- docs/index.md: Tech Stack
Unchanged:
- docs/getting-started/quickstart.md
The sync rules are defined in ${SKILL_DIR}/config/sync_rules.json.
Add a new rule:
{
"id": "new-rule",
"source": {"file": "SOURCE.md", "section": "Section Name"},
"targets": [
{"file": "TARGET.md", "section": "Target Section"}
]
}
documentation
Creates comprehensive handoff documentation before a /compact operation, enabling a new agent with fresh context to seamlessly continue the work. Activate when the user says "prepare a handoff", "document before compact", "context is getting too large", "I need to hand this off", "create a handoff document", "end of session notes", or "document the current state for tomorrow". Supports --output and --linear-issue options.
documentation
Collects completed tasks, GitHub activity, calendar meetings, wiki learnings, and Linear progress for the past week, then writes a structured retrospective to the Obsidian vault. Activate when the user runs "/weekly-review", asks "what did I accomplish this week", "weekly retrospective", "summarise my week", or "prepare weekly review". Works from any directory.
development
Produces a prioritised daily briefing by aggregating tasks from Obsidian TaskNotes, Google Calendar, Gmail, Linear, and GitHub, then writes the result to today's daily note in the Obsidian vault. Activate when the user runs "/today", asks "what's on my plate today", "give me my daily briefing", "what do I need to do today", or "morning briefing". Works from any directory without requiring Obsidian to be running.
tools
Provides a quick status snapshot of all GitHub repositories in a configured organisation — active, dormant, stalled — plus open pull requests and issues. Terminal output only, optimised for speed. Activate when the user runs "/project-pulse", asks "what is the status of my GitHub projects", "show me my repos", "which projects are active", "project overview", "GitHub pulse", or "what is happening in [org]". Works from any directory.