odoo-dev

Plugin odoo-dev from marketplace devcontainer-features in Crpaxton4/devcontainer-features. Commands read from the repo's manifest — 13 days ago.

Skills (16)

• discovery-notes

  Capture and structure client discovery for an Odoo engagement, mining Odoo chatter and knowledge articles first. Use for a discovery or requirements call, current process, actors, volumes, integrations, pain points, or gap analysis before scoping.

• estimate

  Produce an hours estimate: Low/High per leaf snapped to the Fibonacci ladder, parents carrying the raw sum with the nearest Fibonacci beside it, cited anchors, assumptions, exclusions, recorded adjustments. Use for \"estimate this\", \"how many hours\", \"re-cut the numbers\", \"size this change\".

• odoo-code-review

  The Odoo domain lens over module and addon code, in addition to a generic review and never instead. Covers ORM anti-patterns, sudo() misuse, raw-SQL injection, N+1 and prefetch, ir.model.access.csv, record rules, upgrade safety, untranslated strings.

• odoo-design-doc

  Write an Odoo solution or technical design document, discovering current state via read-only Odoo tools first. Use to design or spec an Odoo feature, module, or customization: models, fields, views, security, migration, upgrade impact, rollout.

• odoo-devcontainer

  Working reference for this Odoo devcontainer: paths, odoo-bin, odoo.conf, the ORM, security, views and XPath, controllers, QWeb, OWL assets, tests and tours, commit conventions. Use whenever Odoo module code is written, read, run, or debugged here.

• odoo-populate-db

  Seed a local Odoo database from a named model profile (business, sales, inventory, accounting, all), printing the resolved model order first. Use to populate or seed a dev or benchmark database, and when odoo populate exited 0 having silently skipped most models.

• odoo-pr

  Turn a tested Odoo task branch into a client-visible pull request: a local CodeRabbit review agent pass, standard body, self-assigned draft on the right base, link back on the task. This skill IS the PR standard; do not call gh pr create directly.

• odoo-prior-art

  Check whether standard Odoo on the target version, or an OCA module on the customer's series, already does this. Use at the START of any scoping, estimating, or design task, and for 'do we need to build this?'. Verdicts come from greps, never memory.

• odoo-release

  Promote merged Odoo work one hop up the chain (dev, staging, production): manifest of what would ship, DRAFT aggregation PR with the task/PR table and install/update commands, release note on every task. Use to deploy, promote, or cut a release.

• odoo-repo-map

  Resolve an Odoo project to its git repo, base branch, Odoo series, and environment chain (dev → staging → production). Use before cutting a worktree, opening a PR, or planning a release, and when a project is added or renamed.

• odoo-session-db

  Give one session its own throwaway test database name, so two sessions on one task in one project cannot land on the same database. Use before odoo-dev:odoo-test-run whenever more than one session can work in the same project, and when a test database vanished mid-run.

• odoo-task-env

  Stand up the working environment for one Odoo task: find work that already exists, create or reuse an isolated git worktree on the task branch, bring a runnable stack up. Use at the START of implementing any task, and whenever one is picked back up.

• odoo-test-run

  Run an Odoo module's unit tests and HttpCase browser tours on a throwaway database and return machine-checkable evidence: tests executed, tours executed, failure lines. Use before a PR, after a fix, or when a green run never said how many tests ran.

• odoo-upgrade-project

  Human SOP for a whole Odoo upgrade project past the code port: staging database upgrade through upgrade.odoo.com, on-prem restore, cutover, go-live, support tickets and functional requirements. A planning reference.

• odoo-upgrade

  Plan and run code upgrades of custom Odoo modules between major versions (16.0→17.0→18.0→19.0). Use to migrate or port a module or addon, for breaking changes, a module inventory, or an upgrade estimate or plan.

• principles

  Engineering principles indexed as one-liners: safety and correctness, design and architecture, composition and interfaces, code structure, performance, visibility. Use when writing new code, reviewing a diff, or justifying a design choice.

Slash commands (7)

• /odoo-dev:implement

  Implement one Odoo task unattended, from the host's brief to a draft pull request, by chaining the spec, build, test, iterate and pr stages.

• /odoo-dev:plan

  Plan one Odoo task in plan mode — prior-art verdict, acceptance criteria, a step plan with a verify check per step, hours. Approval writes the plan into the task artifacts.

• /odoo-dev:pr

  Open a client-visible draft pull request — one finished Odoo task branch, or a release that promotes merged work from one branch into the next.

• /odoo-dev:task

  Deliver one Odoo task in its own worktree — existing-work check, branch, stack, code and tests, a green self-test, conventional commits.

• /odoo-dev:test

  Produce independent evidence for one Odoo task branch — unit tests and browser tours on a throwaway database, written by the test script, plus the Odoo review lens.

• /odoo-dev:upgrade-implement

  Port one Odoo task's modules to a target series unattended, from the host's brief to a draft pull request, by chaining the upgrade, test, iterate and pr stages.

• /odoo-dev:upgrade

  Port one Odoo task's modules to a target major series — preflight, inventory, prior-art verdict, the port, the workbook, the install loop. Stops at the port.

Subagents (6)

• odoo-dev-builder

  Deliver one Odoo task end to end in its own worktree: the existing-work check, the task branch, a running stack, the module code and its tests, a green self-test run and conventional commits. Dispatch it for "implement task NNN", "start working on this task", "pick that task back up", "add this fiel

• odoo-dev-implementer

  Implement one Odoo task unattended, inside a devcontainer, from the host's brief to a draft pull request. It runs the spec, build, test, iterate and pr stages as it sees fit, never stops to ask, and records each open question with the assumption it made. Dispatch it for "implement task NNN from this

• odoo-dev-pr

  Open the client-visible draft pull request for a finished Odoo task branch, or the draft release PR that promotes merged work from one branch into the next: local CodeRabbit review, standard body, draft on the right base, task notes. Dispatch it for "open the PR", "push it up for the client", "promo

• odoo-dev-tester

  Produce independent, machine-checkable evidence for one Odoo task branch: unit tests and browser tours on a throwaway database, written by the test script, plus the Odoo review lens over the diff. Dispatch it for "does this pass?", "run the tests and the tours", "verify the branch before the PR" and

• odoo-dev-upgrade-implementer

  Port one Odoo task's modules to a target series unattended, from the host's brief to a draft pull request: upgrade, test, iterate, pr. Never stops to ask; records each decision as an assumption. Dispatch it for "upgrade task NNN to 19.0 from this brief" when no human watches. - odoo-upgrade - odoo-p

• odoo-dev-upgrader

  Port custom and OCA Odoo modules to a target major series (16.0, 17.0, 18.0, 19.0): preflight, module and Studio inventory, the prior-art verdict per module, the port in topological order, the workbook and the install loop until green. Dispatch it for "upgrade this module to 18", "port this addon to

Hooks (3)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/bash-allowlist.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/unattended-guard.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/unattended-guard.sh"

Language servers (1)

• odoo

Similar plugins