agentsclimarketplace

Odoo porting

Skill wpmoo-org/odoo-skills/skills/odoo-porting

Agent Skills for Odoo, OCA-compatible addon development, porting, and open-core Odoo products.

Install
npx -y skills add wpmoo-org/odoo-skills --skill odoo-porting

Assembled 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 forward-porting or backporting Odoo addons between Odoo version branches, especially OCA-style branches such as 13.0 through 19.0.

SKILL.md

2.7 KB, as published. Nobody here has run it

Odoo Addon Porting

Use this skill when moving addon changes between Odoo major-version branches.

Branch rules

  • OCA-style branches are named after Odoo versions: 13.0 through 19.0.
  • Prefer forward-porting one version at a time, for example 17.0 -> 18.0 -> 19.0.
  • Do not mix unrelated features while porting.
  • Keep the source branch and target branch histories reviewable.

Port checklist

  1. Confirm source and target Odoo versions.
  2. Review manifest version and dependencies.
  3. Review Python API changes for the target Odoo version.
  4. Review XML view syntax changes for the target Odoo version.
  5. Review security CSV and record rules.
  6. Install/update the addon in the target version.
  7. Run available tests and pre-commit checks.

Version routing

  • Load the target version skill before changing syntax-sensitive code: odoo-13, odoo-14, odoo-15, odoo-16, odoo-17, odoo-18, or odoo-19.
  • Odoo 13 and 14 ports often involve legacy decorators, data ordering, asset XML inheritance, and multi-company behavior.
  • Odoo 15 and 16 ports must review manifest asset bundles while keeping <tree> list views and attrs/states.
  • Odoo 17 ports must convert view modifiers to direct expressions while keeping <tree>.
  • Odoo 18 and 19 ports must convert list view roots and action modes to <list> and list,form.
  • Odoo 19 ports must review ORM/API changes such as models.Constraint, Domain usage, and JSON-RPC route naming.

Tooling

If oca-port is available and the repository follows OCA conventions, prefer it for repetitive porting mechanics. Still review the result manually.

When a repository uses WPMoo tooling, use the current command standard in examples and instructions:

  • Use npx @wpmoo/toolkit ... for day-to-day workspace commands.
  • Use ./moo ... inside generated Odoo development environments.
  • Run doctor before environment-sensitive porting work.
  • Use snapshot before porting or migration experiments and restore-snapshot when returning to a saved local state.
  • Use resetdb for clean target-version install/update checks.
  • Use lint for configured project checks.
  • Use pot when the port changes translatable strings.

Do not recommend @wpmoo/odoo or @wpmoo/odoo-dev except in explicit deprecated-compatibility documentation.

Done criteria

  • Target branch has the intended functional change only.
  • Manifest version starts with the target Odoo version.
  • Addon installs/updates cleanly in the target Odoo version.
  • Tests and pre-commit checks pass or limitations are reported clearly.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.