Python Oddo Skills

Code style:

• Keep existing comments – do NOT remove them
• Add docstrings to all new methods
• File naming: no _ext suffix (e.g., sale_order_line.py not sale_order_line_ext.py)
• Seed data in default_data.xml with noupdate="1"

Testing:

• make test must pass (all unit tests) after every change
• make reset must work (clean install) after every change
• make smoke must pass (E2E flow) after every change
• make quality must pass (code linting) after every change
• Bank accounts in tests: search for existing before creating (avoid duplicate IBAN errors)
• Cash rounding in tests: ensure profit/loss accounts are set

Boundaries

• Do NOT include implementation code examples (agent knows how to code)
• Keep it concise – bullet points, not paragraphs
• Focus on ERRATA (what's different/broken) not tutorials
• Odoo 19 forbids QWeb directives (t-if, t-else, t-foreach, t-esc, t-field, t-raw) in XML view definitions (form, list, search). These directives are only allowed in QWeb report templates (PDF invoices, delivery slips).

Rule for t-directives in XML files:

9. Performance Tips

1. Prefetch: Access related fields together to benefit from prefetching
2. Batch operations: Use write/create with multiple records
3. Avoid loops: Use recordset operations instead of loops
4. Store computed fields: Store when frequently accessed
5. Indexes: Add indexes to frequently searched fields
6. Limit queries: Use proper domains to limit result sets

10. Debugging

import logging
_logger = logging.getLogger(__name__)

# Log messages
_logger.info('Info message')
_logger.warning('Warning message')
_logger.error('Error message')

# Debug with pdb
import pdb; pdb.set_trace()