菜单
Look up idiomatic approaches, best practices, and common patterns for a given scenario using Exa web search and GitHub code search. Use when user wants to know what's idiomatic, recommended, or common for a bug, architecture decision, library usage, or design pattern.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
| name | lookup |
| description | Look up idiomatic approaches, best practices, and common patterns for a given scenario using Exa web search and GitHub code search. Use when user wants to know what's idiomatic, recommended, or common for a bug, architecture decision, library usage, or design pattern. |
| argument-hint | <question or scenario to lookup> |
| allowed-tools | Bash(gh search *), Bash(gh api *), Agent, mcp__exa__web_search_exa, mcp__exa__crawling_exa, mcp__github__search_code, mcp__github__search_repositories, mcp__github__search_issues, mcp__github__get_file_contents |
Find idiomatic, recommended, and common approaches for a given scenario by searching the web and real-world codebases.
pwdls package.json go.mod Cargo.toml pyproject.toml requirements.txt Gemfile mix.exs build.gradle pom.xml 2>/dev/null | head -5Research the scenario described in $ARGUMENTS. Your goal is to find what real projects actually do — not just what docs say.
Parse the user's query to identify:
Launch parallel searches across multiple sources:
Use mcp__exa__web_search_exa to find:
Search with 2-3 varied queries to cover different angles (e.g. "idiomatic X pattern", "X best practice", "X vs Y tradeoffs").
Use gh search code or mcp__github__search_code to find:
Target repos with stars/activity. Use language filters.
# Example searches
gh search code "pattern query" --language=go --sort=indexed -- -test -example
gh search code "pattern query" --language=go -- -test -vendor
Search for related issues or discussions:
gh search issues "query" --sort=comments --limit=5
If Exa search surfaces particularly relevant pages, use mcp__exa__crawling_exa to read the full content of the top 2-3 results.
Present findings as:
What most sources agree on — the dominant/idiomatic approach.
| Approach | Used By | Pros | Cons |
|---|---|---|---|
| ... | [real repos/authors] | ... | ... |
Show 2-3 concrete code snippets from real repos (with attribution).
Your recommendation for the user's specific context, considering their codebase and constraints.
Bulleted list of the most useful links found.