docs

Use when docs changes are ready to review before opening a PR. Reviews git diff for repetition, structural completeness, logic errors, and style consistency with related pages. Runs trunk fmt and trunk check.

Use when starting a new docs page to scaffold a structured outline. Extracts page type, title, and context from your message, asks only for missing information, then generates a file with sections pre-filled with initial content (1-2 sentences) and focused TODO comments for expansion. Prefer this to the write-docs skill when there is no prior specification.

Process notes, Slack threads, Slite docs, or trunk2 deploy context into documentation changes. Creates a branch, edits docs, opens a PR, and updates Linear. Use when given a notes file from .claude/drafts/, trunk2 PR numbers, Linear ticket IDs, a deploy tag, Slite doc links, or when the user says "write docs", "document this", or "process drafts".