odoo-upgrade

ahmed-lakosha/odoo-upgrade-skill · updated Apr 22, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-upgrade
0 commentsdiscussion
summary

Activate when:

skill.md

Odoo Upgrade Assistant v5.0

When to Use

Activate when:

  • Upgrading Odoo modules between versions (14-19)
  • Fixing version compatibility errors
  • Migrating themes or custom modules
  • Resolving RPC service errors in frontend
  • Converting XML views (tree->list, search groups)
  • Updating SCSS variables for Odoo 18/19 themes
  • Fixing portal view XPath inheritance errors
  • Migrating JavaScript from OWL v1 to v2

Upgrade Workflow

  1. Analyze - Read __manifest__.py, identify source version, scan all files
  2. Backup - Create timestamped backup before changes
  3. Pre-check - Run scripts/cli.py precheck <path> --target <version> to identify all issues
  4. Transform - Apply transforms in order: manifest, XML, Python, JS, SCSS
  5. Validate - Run scripts/cli.py validate <path> to check syntax
  6. Test - Install module: python -m odoo -d DB -i MODULE --stop-after-init

XML/View Transformations

Tree to List (Odoo 19)

<!-- Tags -->        <tree> -> <list>,  </tree> -> </list>
<!-- view_mode -->   tree,form -> list,form
<!-- XPath -->       //tree -> //list
<!-- Remove -->      edit="1" attribute

Search Views (Odoo 19)

Remove <group> tags - place filters at root level. Add <separator/> before group_by filters.

Kanban Templates (Odoo 19)

t-name="kanban-box" -> t-name="card". Remove js_class="crm_kanban".

Cron Jobs (Odoo 19)

Remove <field name="numbercall"> - field no longer exists.

Form View Context (Odoo 19)

active_id -> id in context expressions.

Snippet Options (Odoo 19)

Remove templates inheriting website.snippet_options - system redesigned.

Attrs to Inline (Odoo 18/19)

attrs="{'invisible': [('state','=','draft')]}" -> invisible="state == 'draft'"

Python API Migrations

Slug/Unslug (Odoo 18+)

# Old: from odoo.addons.http_routing.models.ir_http import slug
# New: use request.env['ir.http']._slug(value)

URL For (Odoo 19)

# Old: from odoo.addons.http_routing.models.ir_http import url_for
# New: self.env['ir.http']._url_for('/path')

Controller Type (Odoo 19)

type='json' -> type='jsonrpc' in @http.route decorators.

View Mode (Odoo 19)

'view_mode': 'tree' -> 'view_mode': 'list' in Python dicts.

JavaScript/OWL Migrations

RPC Service (Odoo 19)

RPC service is NOT available in frontend/public components. Replace useService("rpc") with a _jsonRpc helper method using the fetch API with CSRF token handling.

OWL Lifecycle Hooks (Odoo 18+)

OWL 1.x (Odoo 14-17) OWL 2.0 (Odoo 18+)
constructor(parent, props) setup()
willStart() onWillStart(callback)
mounted() onMounted(callback)
patched() onPatched(callback)
willUnmount() onWillUnmount(callback)
willUpdateProps() onWillUpdateProps(callback)

Theme SCSS Variables (Odoo 19)

Use $o-theme-* prefixed variables instead of bare Bootstrap names:

  • $headings-font-weight -> $o-theme-headings-font-weight
  • $font-size-base -> $o-theme-font-size-base

Color palettes must include 'menu', 'footer', 'copyright' assignments:

$o-color-palettes: map-merge($o-color-palettes, (
    'my_theme': (
        'o-color-1': #124F81,
        'menu': 1,
        'footer': 4,
        'copyright': 5,
    ),
));

Portal View XPath Migration (Odoo 19)

Sale portal templates restructured with named selectors:

Headers: th[@id='product_qty_header'], th[@id='product_unit_price_header'], th[@id='product_discount_header'], th[@id='taxes_header'], th[@id='subtotal_header']

Body: tr[@name='tr_product'], td[@name='td_product_name'], td[@name='td_product_quantity'], td[@name='td_product_priceunit'], td[@name='td_product_discount'], td[@name='td_product_taxes'], td[@name='td_product_subtotal']

Mail Template Migration (Odoo 19)

Remove env parameter from format helpers:

<!-- Old --> format_datetime(env, object.date_start)
<!-- New --> format_datetime(object.date_start)

XML entity encoding - use numeric references: &copy; -> &#169;, &nbsp; -> &#160;, &mdash; -> &#8212;

Bootstrap 4 to 5 Class Migration

Bootstrap 4 Bootstrap 5
ml-*/mr-* ms-*/me-*
pl-*/pr-* ps-*/pe-*
text-left/text-right text-start/text-end
float-left/float-right float-start/float-end
sr-only visually-hidden
badge-primary bg-primary
font-weight-bold fw-bold
no-gutters g-0

Data Migration Scripts

Place migration scripts under module/migrations/VERSION/:

  • pre-migrate.py - Before ORM update (use raw SQL only)
  • post-migrate.py - After ORM update (can use env/ORM)
  • end-migrate.py - After all modules updated (cleanup)

Each must define def migrate(cr, version): and guard with if not version: return.

Common patterns:

Pattern Pre-Migrate Post-Migrate
Field rename ALTER TABLE RENAME COLUMN Update views
Selection to M2O Backup values Map to records
Add required field Nothing Populate defaults
Model rename Rename table + ir_model_data Update foreign keys

With openupgradelib: rename_fields(), rename_models(), rename_xmlids(), rename_columns(), logged_query().

Common Errors Quick Reference

Error Cause Fix
Service rpc not available useService("rpc") in frontend Replace with _jsonRpc helper
Invalid field numbercall Field removed Remove from cron XML
Invalid view definition (search) <group> in search Remove group tags
Missing card template kanban-box renamed Use t-name="card"
Cannot import slug Import moved Use compatibility wrapper
website.snippet_options not found System redesigned Remove the template
active_id not found Context change Replace with id

Version-Specific Notes

Odoo 14 to 15

Bootstrap 4.x -> 5.x, t-use-call removed, payment provider API changes, left/right -> start/end

Odoo 15 to 16

Bootstrap 5.1.3 standardized, web framework reorg, OWL v1 adoption begins

Odoo 16 to 17

OWL v1 fully adopted, widget system changes, publicWidget API stabilization

Odoo 17 to 18

OWL v1 -> v2 starts, minor XML changes, snippet group system introduced

Odoo 18 to 19

Major frontend overhaul: RPC service removed, snippet system overhauled, kanban-box->card, search banned, tree->list, portal templates restructured, mail template helpers changed, cron numbercall removed

References

how to use odoo-upgrade

How to use odoo-upgrade on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add odoo-upgrade
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-upgrade

The skills CLI fetches odoo-upgrade from GitHub repository ahmed-lakosha/odoo-upgrade-skill and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/odoo-upgrade

Reload or restart Cursor to activate odoo-upgrade. Access the skill through slash commands (e.g., /odoo-upgrade) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.646 reviews
  • Daniel Yang· Dec 16, 2024

    Keeps context tight: odoo-upgrade is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kwame Shah· Dec 12, 2024

    odoo-upgrade has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Alexander Agarwal· Dec 12, 2024

    Registry listing for odoo-upgrade matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Jin Abbas· Dec 8, 2024

    Solid pick for teams standardizing on skills: odoo-upgrade is focused, and the summary matches what you get after install.

  • Jin Rahman· Nov 15, 2024

    We added odoo-upgrade from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Noor Singh· Nov 7, 2024

    odoo-upgrade is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Advait Thompson· Nov 3, 2024

    Useful defaults in odoo-upgrade — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Charlotte Ndlovu· Nov 3, 2024

    odoo-upgrade reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Daniel Martin· Oct 26, 2024

    Useful defaults in odoo-upgrade — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aisha Garcia· Oct 22, 2024

    odoo-upgrade is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 46

1 / 5