lookup

Route code-understanding questions to LSP, ast-grep, Context7, or octocode.

2|Updated Sep 12, 2016

Search Tags:#routing #lsp #ast-grep #context7 #code-search #code-intelligence #octocode

Ready to run

npx skills add https://github.com/paulnsorensen/dotfiles --skill lookup-paulnsorensen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lookup
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/lookup
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill lookup-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes code-understanding questions to the most suitable analysis tool to avoid wasteful grep-and-doc cycles.

Core Features & Use Cases

Routing to the right tool: LSP for types and references, ast-grep for structural patterns, Context7 for external docs, and octocode for code search.
Quick decision for local vs external code: determine whether to inspect symbols, definitions, or documentation before diving into code.
Use case: when you need to understand a symbol, type, or API, this routing tells you which tool to use instead of grepping or manually searching.

Quick Start

Ask a question about a symbol, type, or API and let the routing decide the best tool to use.

Frequently Asked Questions about lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find the right code intelligence tool for understanding a symbol or API?▼

Code intelligence routing directs symbol, type, or API questions to the most suitable analysis tool—such as LSP, ast-grep, Context7, or octocode—determining whether to inspect definitions, structural patterns, or external docs before you start searching.

What is the best way to avoid wasteful grep-and-doc cycles when analyzing code?▼

Routing code-understanding questions to the right tool avoids wasteful grep-and-doc cycles by returning a deterministic decision on whether to use LSP for types, ast-grep for structural patterns, Context7 for external docs, or octocode for public code search.

Does code routing work with all languages supported by LSP?▼

Yes, routing operates across all languages supported by LSP, directing symbol detail queries to LSP hover and go-to-definition features while routing structural pattern matching to ast-grep and external API documentation to Context7.

How do I route code search tasks between local symbol inspection and external documentation?▼

Routing local versus external code questions selects the appropriate tool based on context, directing local symbol and definition inspections to LSP, structural patterns to ast-grep, and external library documentation to Context7 or public code search to octocode.

When should I use ast-grep instead of LSP for code understanding?▼

Use ast-grep for identifying structural code patterns, while reserving LSP for resolving specific symbol types, hover details, and go-to-definition queries based on the routing decision provided for your code-understanding question.

Does the code routing skill execute the target analysis tool automatically?▼

No, code routing returns a deterministic routing decision identifying the most suitable analysis tool without executing the target tool, leaving the actual code search, symbol inspection, or documentation retrieval to be performed separately.