Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.
中文简介正在准备中。当前显示英语简介。
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
安装前可以查看交给 AI 代理的指令内容。
Use $analyze to answer a repository question with grounded, read-only evidence. Explain what the code most likely says; do not turn analysis into implementation or generic fix planning.
Shared operating, delegation, state, hook, team, cancellation, and verification invariants live in templates/AGENTS.md. Follow that source instead of duplicating its rules here.
Do not use it for edits, implementation, a new product plan, a simple one-file lookup, or OMX team-runtime operation.
Label every material claim as one of:
Prefer direct paths and independent corroboration over contextual clues. Never present guesses as evidence or inference, and never overclaim certainty.
Answer the asked question first and use this shape:
Restated question, briefly.
| Rank | Explanation | Confidence | Basis |
|---|---|---|---|
| 1 | ... | High / Medium / Low | strongest supporting evidence |
| 2 | ... | High / Medium / Low | why it trails |
| 3 | ... | High / Medium / Low | why it remains possible |
path/to/file:line-line — direct observation.path/to/file:line-line — corroborating observation.Task: {{ARGUMENTS}}
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
中文简介正在准备中。当前显示英语简介。
Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.
中文简介正在准备中。当前显示英语简介。
Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.
中文简介正在准备中。当前显示英语简介。
Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.
中文简介正在准备中。当前显示英语简介。
Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.
中文简介正在准备中。当前显示英语简介。
Research recommended practices for a chosen technology using official documentation and maintainer sources. Get a cited recommendation that explains version context, local project constraints, uncertainties, and the next steps for planning or implementation.
中文简介正在准备中。当前显示英语简介。