ahmed-lakosha/odoo-plugins
Overview
This skill is an Odoo upgrade assistant that automates and guides module and theme migrations between Odoo 14–19. It detects common compatibility patterns and provides concrete fixes for XML views, Python API changes, OWL/JavaScript updates, SCSS theme variables, and database migration pitfalls. Use it to reduce manual refactoring and speed safe upgrades to Odoo 17/18/19.
How this skill works
It analyzes a module's structure, manifest, XML, Python, JS, and SCSS files and flags version-incompatible constructs. The skill applies automated transformations or suggests patch snippets for view templates (tree→list), search views, XPath expressions, cron definitions, manifest fields, and OWL lifecycle hooks. For frontend code it replaces deprecated RPC usage with a secure fetch-based JSON-RPC helper and offers OWL 1→2 lifecycle and import adjustments. It also generates manifest and theme variable updates required by Odoo 18/19.
When to use it
- Upgrading custom or community modules between Odoo 14 and 19
- Fixing view errors after migrating to Odoo 18 or 19 (list/tree, search, XPath)
- Migrating frontend components from OWL 1.x to OWL 2.0 or removing useService('rpc')
- Converting or modernizing theme SCSS variables and palette structure for Odoo 19
- Resolving portal template XPath inheritance and mail helper incompatibilities
Best practices
- Create a full code and database backup before applying automated fixes
- Run the analysis step first to get a prioritized list of high-risk changes
- Update __manifest__.py to Odoo 19 conventions (author, website, support, license, assets) before installing
- Refactor JS gradually: add JSON-RPC fetch helper and migrate OWL hooks in small commits
- Validate views and XPath changes in a staging environment and run the testing checklist
Example use cases
- Convert legacy <tree> views to <list> with corresponding action.view_mode updates and XPath fixes
- Replace useService('rpc') calls in public/frontend components with a fetch-based _jsonRpc wrapper
- Migrate OWL 1 lifecycle methods to OWL 2 hooks and update imports for Odoo 18/19
- Refactor theme SCSS: move primary variables into web._assets_primary_variables and rebuild palette map-merge entries
- Remove deprecated cron numbercall fields and fix invalid search view <group> usage
FAQ
No. The skill focuses on code and view migrations. Schema changes that require data migration are identified and suggested, but you should perform database migrations and backups manually or with a dedicated migration tool.
Can automated fixes break custom business logic?
Automated fixes target syntactic and API-level incompatibilities. Business logic semantics may require manual review. Always run tests and review diffs before deploying to production.
6 skills
This skill guides you through upgrading Odoo modules across versions 14 to 19, handling XML, Python, JS, SCSS, and database migrations.
This skill streamlines advanced Odoo frontend theme creation and auto-detection across versions, delivering production-ready themes with reusable patterns and
This skill helps you manage Odoo i18n by extracting strings, validating po files, and generating multilingual reports across versions 14-19.
This skill helps you create, validate, and migrate Odoo email templates and QWeb reports across versions 14-19 with RTL and bilingual support.
This skill streamlines Odoo testing across versions 14-19 by generating test skeletons, running suites, creating mock data, and analyzing coverage.
Comprehensive Odoo ERP upgrade assistant for migrating modules between Odoo versions (14-19). Handles XML views, Python API changes, JavaScript/OWL components, theme SCSS variables, and manifest updates. Use when user asks to upgrade Odoo modules, fix version compatibility issues, migrate themes between versions, or resolve Odoo 17/18/19 migration errors. Specializes in frontend RPC service migrations, view XML transformations, and theme variable restructuring.
