[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHR3GF8DK2MPVN7TBPY643":3,"skill-same:01M7EHR3GF8DK2MPVN7TBPY643":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EHR3GF8DK2MPVN7TBPY643","odoo-upgrade-advisor",null,"Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbusiness\u002Fodoo-upgrade-advisor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-upgrade-advisor\ndescription: \"Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.\"\nrisk: safe\nsource: \"self\"\ndate_added: \"2026-09-04\"\n---\n\n# Odoo Upgrade Advisor\n\n## Overview\n\nUpgrading Odoo between major versions (e.g., v15 → v16 → v17) requires careful preparation, testing, and validation. This skill provides a structured pre-upgrade checklist, guides you through the upgrade tools (Odoo Upgrade Service and OpenUpgrade), and gives you a post-upgrade validation protocol.\n\n## When to Use This Skill\n\n- Planning a major Odoo version upgrade.\n- Identifying which custom modules need to be migrated.\n- Running the upgrade on a staging environment before production.\n- Validating the system after an upgrade.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-upgrade-advisor`, state your current and target version.\n2. **Plan**: Receive the full upgrade roadmap and risk assessment.\n3. **Execute**: Get a step-by-step upgrade command sequence.\n\n## Upgrade Paths\n\n| From | To | Supported? | Tool |\n|---|---|---|---|\n| v16 | v17 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v15 | v16 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v15 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v17 | ⚠️ Multi-hop | v14→v15→v16→v17 (cannot skip) |\n| v13 or older | any | ❌ Not supported | Manual migration required |\n\n## Examples\n\n### Example 1: Pre-Upgrade Checklist\n\n```text\nBEFORE YOU START:\n  ☑ 1. List all installed modules (Settings → Technical → Modules)\n        Export to CSV and review for custom\u002FOCA modules\n  ☑ 2. Check OCA compatibility matrix for each community module\n        https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status\n  ☑ 3. Take a full backup (database + filestore) — your restore point\n  ☑ 4. Clone production to a staging environment\n  ☑ 5. Run the Odoo Upgrade pre-analysis:\n        https:\u002F\u002Fupgrade.odoo.com\u002F → Upload DB → Review breaking changes report\n  ☑ 6. Review custom modules against migration notes\n        (use @odoo-migration-helper for per-module analysis)\n  ☑ 7. Upgrade and test in staging → Fix all errors → Re-test\n  ☑ 8. Schedule a production maintenance window\n  ☑ 9. Notify users of scheduled downtime\n  ☑ 10. Perform production upgrade → Validate → Go\u002FNo-Go decision\n```\n\n### Example 2: Community Upgrade with OpenUpgrade\n\n```bash\n# Clone OpenUpgrade for the TARGET version (e.g., upgrading to v17)\ngit clone https:\u002F\u002Fgithub.com\u002FOCA\u002FOpenUpgrade.git \\\n  --branch 17.0 \\\n  --single-branch \\\n  \u002Fopt\u002Fopenupgrade\n\n# Run the migration against your staging database\npython3 \u002Fopt\u002Fopenupgrade\u002Fodoo-bin \\\n  --update all \\\n  --database odoo_staging \\\n  --config \u002Fetc\u002Fodoo\u002Fodoo.conf \\\n  --stop-after-init \\\n  --load openupgrade_framework\n\n# Review the log for errors before touching production\ntail -200 \u002Fvar\u002Flog\u002Fodoo\u002Fodoo.log | grep -E \"ERROR|WARNING|Traceback\"\n```\n\n### Example 3: Post-Upgrade Validation Checklist\n\n```text\nAfter upgrading, validate these critical areas before going live:\n\nAccounting:\n  ☑ Trial Balance totals match the pre-upgrade snapshot\n  ☑ Open invoices, bills, and payments are accessible\n  ☑ Bank reconciliation can be performed on a test statement\n\nInventory:\n  ☑ Stock valuation report matches pre-upgrade (run Inventory Valuation)\n  ☑ Open Purchase Orders and Sale Orders are visible\n\nHR \u002F Payroll:\n  ☑ All employee records are intact\n  ☑ Payslips from the last 3 months are accessible and correct\n\nCustom Modules:\n  ☑ Every custom module loaded without ImportError or XML error\n  ☑ Run the critical business workflows end-to-end:\n      Create sale order → confirm → deliver → invoice → payment\n\nUsers & Security:\n  ☑ User logins work correctly\n  ☑ Access rights are preserved (spot-check 3-5 users)\n```\n\n## Best Practices\n\n- ✅ **Do:** Always upgrade on a **copy of production** (staging) first — never the live instance.\n- ✅ **Do:** Keep the old version running until the new version is **fully validated and signed off**.\n- ✅ **Do:** Check OCA's migration status page: [OCA Migration Status](https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status)\n- ✅ **Do:** Use the [Odoo Upgrade Service](https:\u002F\u002Fupgrade.odoo.com\u002F) pre-analysis report to get a list of breaking changes **before writing any code**.\n- ❌ **Don't:** Skip intermediate versions — Odoo requires sequential upgrades (v14→v15→v16→v17).\n- ❌ **Don't:** Upgrade custom modules and Odoo core simultaneously — adapt Odoo core first, then fix custom modules.\n- ❌ **Don't:** Run OpenUpgrade against production directly — always test on a staging copy first.\n\n## Limitations\n\n- Covers **v14–v17** only. Versions v13 and older have a fundamentally different module structure and require manual migration.\n- **Enterprise-exclusive module changes** (e.g., `sign`, `account_accountant`) may have undocumented breaking changes not included in OpenUpgrade.\n- The **Odoo.sh** automated upgrade path has a separate workflow (managed from the Odoo.sh dashboard) not covered here.\n- OWL JavaScript component migration (legacy widget → OWL v16+) is a complex front-end topic beyond the scope of this skill.\n","# Odoo Upgrade Advisor\n\n## Overview\n\nUpgrading Odoo between major versions (e.g., v15 → v16 → v17) requires careful preparation, testing, and validation. This skill provides a structured pre-upgrade checklist, guides you through the upgrade tools (Odoo Upgrade Service and OpenUpgrade), and gives you a post-upgrade validation protocol.\n\n## When to Use This Skill\n\n- Planning a major Odoo version upgrade.\n- Identifying which custom modules need to be migrated.\n- Running the upgrade on a staging environment before production.\n- Validating the system after an upgrade.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-upgrade-advisor`, state your current and target version.\n2. **Plan**: Receive the full upgrade roadmap and risk assessment.\n3. **Execute**: Get a step-by-step upgrade command sequence.\n\n## Upgrade Paths\n\n| From | To | Supported? | Tool |\n|---|---|---|---|\n| v16 | v17 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v15 | v16 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v15 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v17 | ⚠️ Multi-hop | v14→v15→v16→v17 (cannot skip) |\n| v13 or older | any | ❌ Not supported | Manual migration required |\n\n## Examples\n\n### Example 1: Pre-Upgrade Checklist\n\n```text\nBEFORE YOU START:\n  ☑ 1. List all installed modules (Settings → Technical → Modules)\n        Export to CSV and review for custom\u002FOCA modules\n  ☑ 2. Check OCA compatibility matrix for each community module\n        https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status\n  ☑ 3. Take a full backup (database + filestore) — your restore point\n  ☑ 4. Clone production to a staging environment\n  ☑ 5. Run the Odoo Upgrade pre-analysis:\n        https:\u002F\u002Fupgrade.odoo.com\u002F → Upload DB → Review breaking changes report\n  ☑ 6. Review custom modules against migration notes\n        (use @odoo-migration-helper for per-module analysis)\n  ☑ 7. Upgrade and test in staging → Fix all errors → Re-test\n  ☑ 8. Schedule a production maintenance window\n  ☑ 9. Notify users of scheduled downtime\n  ☑ 10. Perform production upgrade → Validate → Go\u002FNo-Go decision\n```\n\n### Example 2: Community Upgrade with OpenUpgrade\n\n```bash\n# Clone OpenUpgrade for the TARGET version (e.g., upgrading to v17)\ngit clone https:\u002F\u002Fgithub.com\u002FOCA\u002FOpenUpgrade.git \\\n  --branch 17.0 \\\n  --single-branch \\\n  \u002Fopt\u002Fopenupgrade\n\n# Run the migration against your staging database\npython3 \u002Fopt\u002Fopenupgrade\u002Fodoo-bin \\\n  --update all \\\n  --database odoo_staging \\\n  --config \u002Fetc\u002Fodoo\u002Fodoo.conf \\\n  --stop-after-init \\\n  --load openupgrade_framework\n\n# Review the log for errors before touching production\ntail -200 \u002Fvar\u002Flog\u002Fodoo\u002Fodoo.log | grep -E \"ERROR|WARNING|Traceback\"\n```\n\n### Example 3: Post-Upgrade Validation Checklist\n\n```text\nAfter upgrading, validate these critical areas before going live:\n\nAccounting:\n  ☑ Trial Balance totals match the pre-upgrade snapshot\n  ☑ Open invoices, bills, and payments are accessible\n  ☑ Bank reconciliation can be performed on a test statement\n\nInventory:\n  ☑ Stock valuation report matches pre-upgrade (run Inventory Valuation)\n  ☑ Open Purchase Orders and Sale Orders are visible\n\nHR \u002F Payroll:\n  ☑ All employee records are intact\n  ☑ Payslips from the last 3 months are accessible and correct\n\nCustom Modules:\n  ☑ Every custom module loaded without ImportError or XML error\n  ☑ Run the critical business workflows end-to-end:\n      Create sale order → confirm → deliver → invoice → payment\n\nUsers & Security:\n  ☑ User logins work correctly\n  ☑ Access rights are preserved (spot-check 3-5 users)\n```\n\n## Best Practices\n\n- ✅ **Do:** Always upgrade on a **copy of production** (staging) first — never the live instance.\n- ✅ **Do:** Keep the old version running until the new version is **fully validated and signed off**.\n- ✅ **Do:** Check OCA's migration status page: [OCA Migration Status](https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status)\n- ✅ **Do:** Use the [Odoo Upgrade Service](https:\u002F\u002Fupgrade.odoo.com\u002F) pre-analysis report to get a list of breaking changes **before writing any code**.\n- ❌ **Don't:** Skip intermediate versions — Odoo requires sequential upgrades (v14→v15→v16→v17).\n- ❌ **Don't:** Upgrade custom modules and Odoo core simultaneously — adapt Odoo core first, then fix custom modules.\n- ❌ **Don't:** Run OpenUpgrade against production directly — always test on a staging copy first.\n\n## Limitations\n\n- Covers **v14–v17** only. Versions v13 and older have a fundamentally different module structure and require manual migration.\n- **Enterprise-exclusive module changes** (e.g., `sign`, `account_accountant`) may have undocumented breaking changes not included in OpenUpgrade.\n- The **Odoo.sh** automated upgrade path has a separate workflow (managed from the Odoo.sh dashboard) not covered here.\n- OWL JavaScript component migration (legacy widget → OWL v16+) is a complex front-end topic beyond the scope of this skill.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","self","2026-09-04","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fbusiness\u002Fodoo-upgrade-advisor","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill odoo-upgrade-advisor",{"tool":39,"command":40},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill odoo-upgrade-advisor",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill odoo-upgrade-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbusiness\u002Fodoo-upgrade-advisor\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]