Odoo 19
Agent Skills for Odoo, OCA-compatible addon development, porting, and open-core Odoo products.
npx -y skills add wpmoo-org/odoo-skills --skill odoo-19Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when creating, editing, reviewing, testing, or porting Odoo 19.0 addons with official Odoo 19 developer APIs and OCA-compatible conventions.
SKILL.md
3.9 KB, as published. Nobody here has run it
Odoo 19.0 Addon Development
Use this skill for Odoo 19.0 work. Keep the target branch, manifest version, runtime commands, and source links pinned to 19.0 unless the user explicitly asks for a cross-version port.
First steps
- Confirm the addon repository branch is
19.0or that the task explicitly targets Odoo 19.0. - Inspect the addon manifest and touched files before editing.
- Prefer official Odoo 19.0 documentation and the
odoo/odoo19.0branch for API behavior. Use OCA sources only for OCA conventions. - If the work is a migration, port, or compatibility fix, read
references/porting-upgrade.mdbefore changing code.
Load references as needed
references/official-sources.md: source map for official Odoo and OCA URLs.references/module-anatomy.md: addon structure, manifests, data ordering.references/backend-orm.md: models, fields, computed fields, constraints, CRUD overrides, command tuples, ORM safety.references/security-data.md: ACLs, record rules, groups, XML/CSV data, external IDs, noupdate records, controller security.references/ui-frontend.md: views, actions, menus, reports, assets, JavaScript, Owl, QWeb, website and controllers.references/testing-quality-oca.md: Odoo tests, JS tests, OCA linting, README fragments, review checklist.references/porting-upgrade.md: upgrade scripts, upgrade utils, forward-port rules, 19.0-specific compatibility checks.
Odoo 19.0 defaults
- Manifest versions must start with
19.0, for example19.0.1.0.0. - List views use the
listroot element;treeis the previous name. - Do not introduce legacy
attrsorstatesXML modifiers. Use direct view expressions such asinvisible,readonly, andrequired. - Prefer
models.Constraint,models.Index, andmodels.UniqueIndexfor new SQL constraints and indexes. - Keep public model methods defensive: public methods can be called through RPC, so validate records, arguments, access rights, and state before side effects.
- Use the 19.0 CLI
module upgrade --outdatedbehavior when the task is about updating only modules with newer manifest versions on disk.
OCA-compatible development rules
- Keep one Odoo major version per branch.
- Keep every addon in a top-level addon directory.
- Use small, composable addons with minimal explicit dependencies.
- Community addons must not depend on private/pro/customer addons.
- Use
LGPL-3orAGPL-3according to repository policy. - Follow OCA manifest versioning:
19.0.x.y.z. - Keep generated
README.rstoutput separate from source fragments when a repo uses OCA README tooling.
Local helper
Run the bundled quick check against an addon or addon repository:
node skills/odoo-19/scripts/validate-addon.mjs /path/to/addons-or-addon
This is a fast heuristic check only. It does not replace installing/updating the addon in an Odoo 19.0 database.
Verification
Use the repository's configured checks first. Common OCA-compatible order:
pre-commit run -a
odoo-bin -d test_db --addons-path=/path/to/addons -i addon_name --test-enable --stop-after-init
odoo-bin -d test_db --addons-path=/path/to/addons -u addon_name --test-enable --stop-after-init
When WPMoo tooling is present, use the current command standard:
npx @wpmoo/toolkit doctor
./moo lint
./moo resetdb
./moo pot
Done criteria
- Manifest version, license, dependencies, data order, and installability match Odoo 19.0.
- Security files grant the minimum required access and record rules are tested.
- Views use Odoo 19.0 syntax and avoid legacy modifiers.
- Python, XML, JS, and translation changes pass configured linters.
- The addon installs or updates cleanly in a 19.0 database with relevant tests.