Claude Code Docs

Local mirror of Anthropic Claude Code documentation, kept fresh by a 3-hour GitHub Action. The cleaned Markdown lives in references/; the auto-generated topic list lives in references/INDEX.md; the per-file manifest with upstream URLs lives in references/docs_manifest.json.

Scope

Use this skill for Claude Code-specific product and configuration questions, including CLI behavior, settings, slash commands, hooks, skills, plugins, MCP, subagents, AGENTS.md, output styles, sandboxing, permissions, environment variables, monitoring and usage, Claude Desktop, Slack, Chrome, Web, Agent SDK, and release notes. If the question is about OpenAI Codex, Cursor, Claude.ai consumer features, the general Anthropic API, or another non-Claude-Code product, this skill does not apply.

Workflow

1. If the user supplied a topic, normalize it to a slug:

- lowercase, strip leading /docs/en/, strip surrounding slashes - join nested segments with (e.g. agent sdk hooks -> agent-sdkhooks, whats new 2026 w19 -> whats-new__2026-w19)

1. If references/<slug>.md exists, read that file directly. Do NOT grep the whole references/ tree first - the index plus targeted reads is faster and uses less context.
2. If no exact match, read references/INDEX.md and pick the closest topic. If still ambiguous, list the candidates and ask.
3. If the user supplied no topic, read references/INDEX.md and present the available topics.

Answer format

• Lead with a direct answer to the user's question grounded in the file you read.
• Quote short snippets (commands, config keys) when they appear verbatim in the doc.
• End with Source: <upstream URL> using the originalurl from the file frontmatter or references/docsmanifest.json.

Freshness and fallback

The mirror is refreshed every 3 hours by upstream CI, which fails rather than committing frozen content. If the local content looks stale, contradicted by the user, or empty:

1. Suggest the user run npx skills update claude-code-docs.
2. Check the file's entry in references/docs_manifest.json: a status of stale means upstream could not be reached on the last run.
3. Cross-check the canonical URL via originalurl in references/docsmanifest.json and offer it as a follow-up source.
4. If a specific page failed MDX cleaning, the unmodified source is preserved at references/_raw/<slug>.md -- read that as a fallback.

Examples