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.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.