odoo-development

MUST be invoked when user asks to "create odoo module", "generate module", "scaffold odoo", "new odoo app". CRITICAL: This command MUST invoke the odoo-context-gatherer agent before generating any code.

Generate OWL components for Odoo frontend. Use when user asks to "create owl component", "add widget", "frontend component", "client action".

MUST be invoked when user asks to "review odoo module", "audit module", "check security", "analyze code quality". CRITICAL: This command MUST invoke the odoo-code-reviewer agent for systematic review. DO NOT perform manual reviews - ALWAYS use the specialized agent.

Generate or audit security configuration for an Odoo module. Use when user asks to "generate security", "add access rights", "create record rules", "audit permissions".

Generate test cases for Odoo models and business logic. Use when user asks to "write tests", "generate unit tests", "test module", "create test cases".

MUST be triggered when reviewing Odoo modules for code quality, security, performance, and version compliance. ALWAYS use this agent for ANY Odoo code review task. CRITICAL: DO NOT review Odoo code manually - this agent MUST be invoked. <example> Context: User asks to review Odoo code user: "Review my Odoo module for security issues" assistant: [MUST invoke odoo-code-reviewer agent] <commentary> Agent performs systematic review against version-specific best practices </commentary> </example> <example> Context: User wants code audit user: "Check my module for performance problems" assistant: [MUST invoke odoo-code-reviewer agent] <commentary> Agent checks for N+1 queries, missing indexes, inefficient patterns </commentary> </example>

MUST be triggered BEFORE any Odoo code generation or modification. CRITICAL: This agent is MANDATORY for ALL Odoo development tasks. ALWAYS invoke this agent when user mentions: - Creating/modifying Odoo modules, models, views, fields - OWL components, JavaScript, QWeb templates - Security, access rights, record rules - Workflows, automations, scheduled actions - ANY Odoo version (14, 15, 16, 17, 18, 19) DO NOT generate Odoo code without first calling this agent. <example> Context: User requests Odoo development user: "Create a computed field for total amount" assistant: [MUST invoke odoo-context-gatherer with task="computed field for total amount"] <commentary> Agent gathers computed field patterns, version-specific syntax, best practices </commentary> </example> <example> Context: User wants to build an Odoo feature user: "Add a sale order workflow with approval" assistant: [MUST invoke odoo-context-gatherer with task="sale order workflow approval"] <commentary> Agent gathers workflow patterns, state management, mail integration, security </commentary> </example> <example> Context: User wants to extend existing functionality user: "Add custom fields to res.partner" assistant: [MUST invoke odoo-context-gatherer with task="custom fields res.partner"] <commentary> Agent gathers inheritance patterns, field types, security considerations </commentary> </example>

MUST be used when odoo-context-gatherer needs to find specific pattern excerpts. ALWAYS returns: FILE path + LINE range + max 50 lines of relevant code. Use this agent for targeted pattern lookups when you need a specific code example without loading entire skill files into context. <example> Context: Need specific computed field pattern user: "How to create editable computed field" assistant: [Invoke odoo-skill-finder to get precise excerpt] <commentary> Returns only the 20-50 lines needed, keeping context clean </commentary> </example>

Specialized agent for analyzing upgrade compatibility between Odoo versions