odoo-devlisted
Install: claude install-skill Aghyksa/odoo-dev
# Odoo Dev
Author: [aghyksa](https://aghyksa.com). Project `AGENTS.md` / `CLAUDE.md` and user instructions win over
this skill. One goal: **never guess**. Every claim about an Odoo API or behavior needs a `file:line` from
the project's own version. Not found → say "not in base", never invent it.
## Tool
`python3 <skill-dir>/scripts/odoo_env.py <cmd>`, where `<skill-dir>` is the folder holding this
`SKILL.md`. Run it from the project. Read-only, stdlib only, Python 3.8+.
| Command | Gives |
|---|---|
| `env` | version, odoo_root, conf, db, python, addons roots. Act on every `note` / `WARNING`, else pass `--conf` |
| `model M`, `field M F`, `xmlid MOD.ID` | where it is defined and extended, in that version |
| `method M NAME` | override chain in load order; flags overrides without `super()` |
| `routes MOD` | each HTTP route with auth, csrf, sudo; flags public + sudo |
| `port-scan PATH --to V` | `file:line` of APIs that break on version V, up or down |
Config lookup order: `--conf`, `$ODOO_RC`, an `odoo-bin -c` entry in `.vscode/launch.json` or
`.claude/launch.json`, a `*.conf` in the project or its parents, then `~/.odoorc` and `$ODOO_CONF_DIRS`
(default `~/odoo/conf:/etc/odoo`). The Odoo source must be on disk (a Docker-only setup: mount or clone
the matching version and pass `--conf`).
## Workflow
1. `env`. If the project has a code graph or index (e.g. `graphify-out/graph.json`), query it before
grep or read.
2. Trace the real definitions (`model` / `field` / `me