Files
claude/skills/doc/SKILL.md
T
bastien 94189adbc6 feat(effort): entry effort level on the 31 user-invoked skills (spec D3)
A/B /reconcile headless — BEFORE requests=18 output=12374 thinking=3135 effort={'high'} duration_ms=96518 / AFTER requests=15 output=9038 thinking=2248 effort={'low'} duration_ms=78410
2026-09-28 19:11:21 +02:00

54 lines
2.2 KiB
Markdown

---
name: doc
effort: low
description: |
Use when documentation may be out of sync with code — features
added/removed vs README / INSTALL / DEPLOY / CHANGELOG. Stack-aware
audit, cross-references git history, patches approved items.
Triggers: "doc", "sync docs", "update readme", "documentation drift",
"stale docs", "docs à jour ?", "create README", "should I have a
DEPLOY doc".
argument-hint: [leave empty for full audit, or list specific files/docs to check]
allowed-tools:
- Read
- Edit
- Write
- Bash
- Grep
- Glob
- Agent
---
Run the two-mode doc pipeline (BDR-077 — audit judgment on opus, patch on
the sonnet pin, the validation gate in THIS loop; a dispatched agent cannot
hold a gate):
0. AIGUILLAGE — before any write, follow `$HOME/.claude/lib/gitflow-aiguillage.md`
— this skill's TYPE = `chore`. On `main`/`develop` it branches to
`chore/<name>` off develop so the doc patch lands on a branch; on a working
branch it proceeds in place. Never `gitflow finish`. `lib/doc-commit.md`'s
rc 5 (commit rejected by the hook on a protected base) stays as the
backstop, not the plan.
1. AUDIT — dispatch:
`Agent(subagent_type="doc-syncer", model="opus")`
prompt: "MODE: audit. Audit public docs for this project. Context from
the user: $ARGUMENTS. Emit the DOC SYNC REPORT + PATCH PLAN — no writes."
2. GATE — present the report and run the DOC SYNC — VALIDATION GATE from
the agent's DISPATCHER PROTOCOL (AUTO yes/select/cancel; HUMAN, CREATE,
CLEAN per-item; README CREATE has no skip). Wait for explicit approval.
`DOC SYNC: all docs current` → stop here.
3. PATCH — re-dispatch:
`Agent(subagent_type="doc-syncer")` (sonnet pin)
prompt: "MODE: patch." + the APPROVED PATCH PLAN verbatim (approved item
lines + rendered drafts for approved CREATE items). A `SHAPE ESCALATION`
in its report → re-gate the named set here, then re-dispatch patch with
the kept subset.
4. COMMIT — from THIS loop per `$HOME/.claude/lib/doc-commit.md` (surgical:
only the report's `PATCHED_FILES`, summary composed from its
`CHANGE SUMMARY` block, never `.claude/`/`CLAUDE.md`, no-op if nothing
patched).