Stats
Actions
Tags
From up-docs
Update all three documentation layers (repo, wiki, Notion) sequentially from the current session. This skill should be used when the user runs /up-docs:all.
How this skill is triggered — by the user, by Claude, or both
Slash command
/up-docs:allThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Update all three documentation layers in sequence: Repo, then Wiki, then Notion.
Update all three documentation layers in sequence: Repo, then Wiki, then Notion.
Gather the session's changes up front, since all three layers draw from the same context:
git diff --stat HEAD~5 HEAD 2>/dev/null || git diff --stat
git log --oneline -10
Combine with conversation history. Build a complete picture of what the session accomplished.
Follow the full procedure from ${CLAUDE_PLUGIN_ROOT}/skills/repo/SKILL.md:
Follow the full procedure from ${CLAUDE_PLUGIN_ROOT}/skills/wiki/SKILL.md:
Follow the full procedure from ${CLAUDE_PLUGIN_ROOT}/skills/notion/SKILL.md (and read ${CLAUDE_PLUGIN_ROOT}/skills/notion/references/notion-guidelines.md before making changes):
Read ${CLAUDE_PLUGIN_ROOT}/templates/summary-report.md for the output format.
Emit one combined report using the /up-docs:all format: a heading per layer, each with its own table and totals line.
Each layer gets the right kind of content:
| Layer | Content Level | Example |
|---|---|---|
| Repo | Project-specific docs | "Added --verbose flag to the CLI" |
| Wiki | Implementation reference | "Authentik OIDC client config for the new service" |
| Notion | Strategic/organizational | "New monitoring service added to the homelab stack" |
If information only belongs in one layer, update only that layer. Not every session change needs to propagate to all three.
npx claudepluginhub l3digitalnet/claude-code-plugins --plugin up-docsImplements two-phase workflow to analyze code changes via git diff and update project documentation. Use before merging branches, after features/bugfixes, or when docs stale.
Entry point for updating tracked llmdoc/ docs after project knowledge, architecture, or workflows change. Selects the appropriate investigation mode and maintains consistent repository documentation.
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.