MIT-licensed Claude Code plugin + IDE snippets for the Odoo Semantic MCP server (Viindoo).
Agent
Use this agent when an orchestrator needs to EXECUTE a local git mutation safely - integration (fetch, pull-rebase, merge, cherry-pick, forward-port, backport, branch/tag/worktree, non-force push) OR a destructive history rewrite (interactive rebase, squash, split, amend, reset, filter-repo, force-with-lease push). It…
Agent
Use this agent when a git/github change is COMPLEX or LARGE - more than 500 files, more than 10,000 lines, a multi-commit history rewrite, or a thousand-file backport/forward-port - and the whole phased pipeline should run BELOW the caller so the caller's context stays pristine. It is the ONLY agent that spawns…
Agent
Use this agent when an orchestrator needs READ-ONLY git cognition - mapping, analyzing, evaluating, or proving - over a repo, a diff range, or a commit history, without mutating anything. Typical triggers include a phased-pipeline P1 map pass (cluster thousands of changed files by module), a P2 per-cluster evaluation…
Agent
Use this agent when an orchestrator needs a GitHub API operation - the PR lifecycle (create, read, review, merge), issue triage (read, write, comment), branch/commit/tag queries, file reads, code search, releases, CI status, or fork -> PR upstream. It uses the GitHub MCP tools as PRIMARY and the gh CLI as fallback…
Agent
Use this agent when the main agent needs to write production-ready Python/XML Odoo backend code - computed fields, ORM overrides, constraints, migration scripts. It implements to a RED test the odoo-test-writer teammate already authored (it does NOT author tests). Dispatched by the odoo-coder per-node coordinator as…
Agent
Use this agent when the main agent needs to diagnose a Python/ORM/server-side Odoo runtime failure to a PROVEN root cause - data-state bugs, Expected singleton, AccessError (ir.model.access vs ir.rule), compute/onchange/constraint/ORM-hook-order bugs, tracebacks, module-load/migration/ParseError. OSM-only (no…
Agent
Use this agent when main agent needs to review existing Odoo Python/JS/XML/OWL code for bugs, convention violations, security issues, N+1 queries. Produces CRITICAL/HIGH/MED/LOW findings + corrected version.
Agent
Use this agent as the COORDINATOR the odoo-coding skill launches for EVERY work node (backend-only, frontend-only, or full-stack; a node may name one module, part of one, or several). For its node it computes an INTERNAL work-item (WI) breakdown - splitting the node's changes into 1..N WIs by DISJOINT file sets …
Agent
Use this agent when an orchestrator needs a structured business behavior (nghiệp vụ) / intent (ý đồ) / expected-outcome / acceptance-criteria comparison between two code states - read-only, writes only its findings file. Typical triggers include odoo-git-rebase P3 dispatching a cluster-level comparison of the feature…
Agent
Use this agent when a documentation package spanning MORE THAN ONE Odoo module needs a dependency-aware execution plan before any instance is provisioned - it partitions the in-scope modules into dependency clusters, allocates instances by DAG SHAPE (a linear chain shares one instance and installs incrementally…
Agent
Use this agent when the odoo-doc-walkthrough skill (or another caller) needs happy-path usage scenarios authored for an Odoo module - structured walkthroughs (role, precondition, step list, expected outcome) grounded in the module's ACTUAL behavior via OSM, ready to drive the odoo-doc-illustration skill CAPTURE MODE…
Agent
Use this agent when the doc pipeline needs to resolve the documentation target, map it to Odoo modules, and produce a compact scope block before dispatching the odoo-doc-illustration skill. Typical triggers include the odoo-doc-illustration skill receiving a TARGET=repo: instruction for a multi-module scan, a…
Agent
Use this agent when the odoo-doc-feature-map skill (or another caller) needs a complete, machine-readable capability inventory for ONE Odoo module done in its OWN context so the orchestrator stays context-clean. It enumerates every user-visible feature a module ships - menus, views, models, actions, key fields, roles…
Agent
Use this agent when main agent needs to write production-ready Odoo frontend code (JavaScript, OWL, QWeb, SCSS) for any supported version - legacy web.Widget/AbstractField/odoo.define() (v8-v14) or OWL 2.x patch()/useState/useService (v15+). Produces complete files + manifest wiring. It implements to a RED JS test the…
Agent
Use this agent when the odoo-gap-analysis skill (or another caller) needs the heavy gap-analysis work for ONE requirement cluster done in its OWN context, so the orchestrator/main stays context-clean. It classifies each requirement against Odoo standard functionality - coverage (full/partial/none), classification…
Agent
Use this agent when the main agent needs to design and generate an Odoo module icon asset - composing a brand-aware, version-correct SVG then rasterizing it to static/description/icon.png (256x256 PNG). Typical triggers: "design an icon for this module", "generate icon.png for ", "create the app icon for this addon"…
Agent
Use this agent when the forward-port pipeline needs to resolve a category-3 ambiguity - the target clean-tip module descriptor shows installable: True for a module, but that manifest was not touched by any commit in the forwarded commit range, so the SOURCE-side manifest history must also be read to confirm whether…
Agent
Use this agent when a human OR another agent needs a live Odoo instance built, dropped, or driven for ANY series from v8 onward - create or drop a database through Odoo, init or update modules, run tests, ensure an instance is up, or report status - and wants structured metadata back including a persistent log path.…
Agent
Use this agent when the main agent needs to extract the business intent, purpose, and behavioral contract from one or more Odoo commits belonging to the SAME module - separating what behavior each commit was designed to produce from its implementation details. Read-only, one MODULE per instance: odoo-forward-port's P1…
Agent
Use this agent when the odoo-doc-illustration skill needs the BUYER-facing App-Store landing page (static/description/index.html) assembled for a single Odoo module - lay out a brand-aware, sanitizer-safe Bootstrap-5 fragment from marketing copy the skill SUPPLIES (pre-drafted by odoo-content-draft) plus the REQUIRED…
Agent
Use this agent to prepare and EXECUTION PLAN for an APPROVED Odoo design / development work authored in its own context - turning the design DAG (daglayers + dependency direction), the gap matrix, and (when already authored) the QA oracle into a gate-able 3-block plan: a dependency-ordered node graph (a node MAY span…
Agent
Use this agent when an orchestrator needs an INDEPENDENT acceptance oracle - test scenarios with chosen-up-front expected results - derived from a requirement/intent, BEFORE the system is exercised. It writes an immutable scenarios.md covering GWT, equivalence/boundary, negative paths, and role/CRUD/state/search…
Agent
Use this agent when an orchestrator needs an acceptance oracle EXECUTED against a real running Odoo instance and adjudicated - driving the live UI across the affected cluster (CRUD, at least two roles, state transitions, search) and ruling each scenario PASS/FAIL/UNVERIFIED with captured evidence. Typical triggers…
Agent
Use this agent when the odoo-code-review skill needs to resolve the review target, map changed files to modules, and produce a compact scope block before dispatching reviewers. Typical triggers include the skill receiving a TARGET=local instruction to scope the current branch diff, a TARGET=worktree: instruction to…