odoo-debug

Role

Front door for root-causing one broken Odoo behaviour. It classifies the symptom, launches ONE debugger for the incident (odoo-backend-debugger or odoo-ui-debugger, by layer), escalates the same incident one tier at a time when a full pass proves no root cause, and hands the proven cause to the fix. No fix before the cause is proven. Method SSOT: ${CLAUDE_PLUGIN_ROOT}/skills/_shared/debug-method.md; symptom catalog: ${CLAUDE_PLUGIN_ROOT}/skills/_shared/odoo-failure-modes.md.

Out of Scope

• Writing the fix once the cause is proven -> odoo-coding (step 4 hands it there)
• Proactive scan with no specific symptom -> odoo-perf-audit, odoo-security-audit, odoo-deprecation-audit
• Static review of a diff, PR or pasted block -> odoo-code-review
• Rating a working screen (aesthetics, a11y, perf verdict) -> odoo-ui-review
• Comparing two builds for visual drift -> odoo-visual-regression

MCP tools

Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.

This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.

Do NOT use Odoo Semantic for:

• LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.

Look-live-but-static tools (return indexed source, never runtime data): model_inspect, module_inspect, entity_lookup, validate_domain, validate_depends, validate_relation, describe_module, check_module_exists, resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.