analyzelisted

# Analyze — Read-Only Deep Analysis Use this skill to answer the user’s question through **read-only repository analysis**. The goal is to explain what the codebase most likely says about the question, not to drift into implementation, debugging theater, or generic fix planning. ## Use `$analyze` when - the user wants a grounded explanation, not code changes - the answer requires reading multiple files or tracing behavior across boundaries - there are several plausible explanations and they need to be ranked - confidence should reflect the strength of the available evidence - the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything Examples: - why a workflow behaves a certain way - how a feature is wired across modules - what likely explains a failure, regression, or mismatch - what would be impacted by changing a dependency or contract - which interpretation of the current codebase is best supported ## Do not use `$analyze` when - the user explicitly wants code edits, a fix, or execution — use the appropriate implementation lane instead - the user wants a new product plan or acceptance criteria — use `$plan` / `$ralplan` - the request is a simple one-file fact lookup — read the file and answer directly - the request is purely about running the OMX tmux team runtime — use `$team` only when OMX runtime is active ## Non-negotiable contract Analyze is **read-only by contract**. - Do not edit files. - Do not turn the a