Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Surface architectural friction and propose deepening opportunities: refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
Use these terms exactly in every suggestion. Full definitions are in LANGUAGE.md.
Key principles:
Read the project's domain glossary and any ADRs in the area first. Then inspect the codebase organically and note where understanding creates friction:
Apply the deletion test to anything suspected of being shallow.
Present a numbered list of deepening opportunities. For each candidate include:
Use CONTEXT.md vocabulary for the domain and LANGUAGE.md vocabulary for architecture. If a candidate contradicts an existing ADR, only surface it when the friction is real enough to warrant revisiting that ADR.
Do not propose interfaces yet. Ask: "Which of these would you like to explore?"
Once the user picks a candidate, walk the design tree: constraints, dependencies, the shape of the deepened module, what sits behind the seam, and what tests survive.
Side effects happen inline as decisions crystallize:
CONTEXT.md, add the term using CONTEXT-FORMAT.md.CONTEXT.md immediately.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me" outside an Odoo-specific context.
The English summary is being prepared. Showing the original description.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against their project's language and documented decisions.
The English summary is being prepared. Showing the original description.
Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo codebase is detected.
The English summary is being prepared. Showing the original description.
Odoo 17 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 17 or custom addons, including traceback diagnosis, addons, manifests, XML errors, HTTP controllers, business rules, feature work, refactoring, or reviews.
The English summary is being prepared. Showing the original description.
Odoo 18 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 18 or custom addons, including traceback diagnosis, addons, manifests, XML errors, HTTP controllers, business rules, feature work, refactoring, or reviews.
The English summary is being prepared. Showing the original description.
Odoo 19 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 19 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices.
The English summary is being prepared. Showing the original description.