Software Development Skills

Review Odoo addon code for correctness, security, performance, migrations, tests, and official Odoo coding guidelines. Use when reviewing Odoo modules, diffs, pull requests, or changed files involving models, fields, XML views, data, controllers, reports, OWL/assets, manifests, access rules, record rules, or OCA migrations.

Use before implementing a non-trivial Odoo feature or design, to pressure-test the approach before any code is written. Symptoms — "I'm about to build X", an underspecified plan, or a design with multi-company / upgrade implications. Interrogates the plan one question at a time, each with a recommended answer, walking the design tree. Not for quick fixes the user already scoped.

Use when writing or reviewing any migrations/ upgrade script, when a diff changes a field or model on a module already deployed to a customer, or when porting a module to a new Odoo major version. Covers when you owe a migration, the util-first rule, pre/post/end timing, the research-then-mechanical-pass order for version ports, and verifying against a real pre-upgrade snapshot.

Use when designing or writing any Odoo module — new models, inherited models, views, security records, migrations, or demo data. Invoke before creating manifest.py or any file under a module directory.

Use when writing or reviewing any Python in an Odoo module — models, computes, overrides, controllers, wizards. Carries PSAE review-derived principles for ORM correctness, performance, style, and security, plus references for exact patterns. Invoke before writing logic in models/, controllers/, or wizard/.

Use when wrapping up a project.task ticket — after writing the code, before claiming done. Orchestrates the code-review pass, the test-runner pass, and a customer-readiness check. Invoke instead of saying "I think it's done.

Use when verifying an Odoo development before claiming "it works," or when writing the tests themselves. Spins up a fresh DB, installs the module, and proves the feature behaves as the ticket asked via --test-enable, the shell, or the UI — and carries the conventions for the tests: class choice, @tagged, assertRecordValues, the demo-user password trap, tours. Invoke whenever tempted to say "it works" without proving it on a clean install, or before adding files under tests/.

Use when writing, reviewing, or migrating any .xml file in an Odoo module — views, actions, menus, security records, data files, QWeb templates. Holds Odoo's naming, formatting, inheritance, and cross-version syntax conventions. Invoke before adding records to views/, security/, data/, or report/ directories.

Use when the user corrects you on Odoo specifics, when you notice a skill missed a real case, or when skills/journal.md has accumulated 5+ entries. Turns concrete corrections into sharper principles in the actual skill files. Invoke after sessions where the user pushed back on Odoo-specific advice.

Use at the start of any Odoo PSDU task to know which Odoo-specific skill to reach for. Covers when to invoke odoo-module-development, odoo-code-review, odoo-test-runner, odoo-task-completion, and refining-odoo-skills. Invoke before writing any Odoo model, view, or migration.