From dig
Clones GitHub repos for libraries, explores source code/docs with research agent to answer API/usage questions. For unfamiliar libraries or 'How do I use X?' queries.
npx claudepluginhub udecode/dotai --plugin digThis skill uses the workspace's default tool permissions.
Look up library documentation by finding and exploring the library's source code repository.
Clones library repositories from GitHub and researches source code with an agent to answer questions about APIs, usage, and documentation.
Retrieves code context summaries, API docs, and examples from GitHub repos, npm/pip libraries, code searches, and clones using isolated agents.
Accesses definitive source code of project dependencies via vector search and direct file reads for API signatures, error debugging, internals, configs, and tests.
Share bugs, ideas, or general feedback.
Look up library documentation by finding and exploring the library's source code repository.
First, check if the library source code already exists locally:
# Check common locations
ls /tmp/cc-repos/{library-name} 2>/dev/null
If the library exists locally, skip to step 3.
If not available locally, find and clone the repository:
mkdir -p /tmp/cc-repos
git clone https://github.com/{owner}/{repo}.git /tmp/cc-repos/{repo-name}
Common repository patterns:
package.json homepage or repository field, or search https://github.com/{package-name}Launch a Research agent (using the Task tool with subagent_type="Explore") to traverse the repository and answer the question.
Example prompt for the agent:
Explore the repository at /tmp/cc-repos/{repo-name} to answer: {user's question}
Focus on:
- README and documentation files
- Source code structure
- API exports and public interfaces
- Examples and tests for usage patterns
Use the research findings to provide a clear, accurate answer to the user's question about the library.