Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From docfork
Fetches up-to-date GitHub documentation for libraries, frameworks, and APIs via search and chunk/TOC retrieval for usage, references, configs.
npx claudepluginhub docfork/docfork --plugin docforkHow this skill is triggered — by the user, by Claude, or both
Slash command
/docfork:docfork-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**library**: Start with a short name or keyword (e.g., `nextjs`, `react router`) — this triggers multi-library search with server-side reranking. Once a result is returned, extract the `owner/repo` from its URL and use that exact form for any follow-up calls to pin to the verified repository.
Retrieves code context summaries, API docs, and examples from GitHub repos, npm/pip libraries, code searches, and clones using isolated agents.
Uses docpull tools to fetch, index, and search live docs for fast-moving libraries like Next.js, FastAPI, LangChain, React when answering 'how to X' or API questions.
Fetches current library documentation, API references, and code examples via Context7 REST API. Use for any library (React, Next.js, Vue, Django, etc.).
Share bugs, ideas, or general feedback.
docfork:search_docslibrary: Start with a short name or keyword (e.g., nextjs, react router) — this triggers multi-library search with server-side reranking. Once a result is returned, extract the owner/repo from its URL and use that exact form for any follow-up calls to pin to the verified repository.
query: Specific and descriptive — e.g., "server actions in Next.js App Router" not "next.js actions". Include version if specified (e.g., "React 19 concurrent features").
Each result returns a title, description, and url. Prefer canonical/official repos over forks. Retry with a broader or different query if results are empty or off-target.
3 calls maximum across the entire request.
docfork:fetch_docSearch results are summaries. Call fetch_doc to get the actual content - this is the default next step after a relevant result, not a last resort.
Two URL modes, both derived from search result URLs:
Exact chunk - pass the URL as-is, keeping the line anchor (#L40-L85):
https://github.com/vercel/next.js/blob/main/docs/routing/middleware.mdx#L40-L85
Table of contents - strip the filename and anchor, pass the parent path:
https://github.com/vercel/next.js/blob/main/docs/routing/
Returns a TOC with previews across that directory - use when you need broader context before committing to a specific chunk.
If a chunk's description is truncated or vague, fetch it - descriptions are previews only.