---

name: external-codebase-research description: External (non-workspace) research protocol. Use network search only to locate canonical repos/docs, then verify by reading source (github_repo) or official docs (Context7/DeepWiki). Enforce fact-driven answers with explicit evidence and version anchoring.

External Codebase Research

Scope

Use for third-party libraries (IsaacSim/PhysX/etc.), external repos, upstream code verification.

Core Rules

1. Fact-driven: No guessing without authoritative sources; state missing evidence explicitly
2. Evidence mandatory: Back claims with docs reference OR repo path + symbol + line range
3. Version matters: Prefer tag/release > commit SHA > branch; flag version uncertainty
4. Token discipline: Web search = discovery only; read minimal files needed

Tool Priority

Official docs (concepts/usage/APIs)

1. Context7 (mcp_io_github_ups_get-library-docs) — mainstream libraries (highest efficiency)
2. DeepWiki (mcp_cognitionai_d_ask_question) — high information density
3. GitHub Repo (github_repo) — when docs insufficient

Source code (exact behavior/defaults/conditionals)

• GitHub Repo (github_repo) — primary evidence

Web search (discovery only)

• Find canonical repos/docs, locate entry points, identify relevant issues

Workflow

1. Restate target: library/repo + question + version constraint
2. Route: Conceptual → DeepWiki; Exact logic → github_repo; Unknown → web discovery first
3. Repo reading: Locate entry points (APIs/configs/registries) → follow chain → extract minimal snippets
4. Output:
   • Findings: verified statements
   • Evidence: docs section OR code path/symbol/lines
   • Next checks (if incomplete): exact files/symbols to inspect

Anti-Patterns

• Inferring without evidence
• Quoting issues/blogs as implementation truth
• Reading large unrelated files
• Mixing versions without labeling