odoo-code-tracer

Trace Odoo execution paths from entry points through method chains.

120|56|Updated Jan 16, 2026

Search Tags:#debugging #api #inheritance #odoo #trace #controllers #code-flow

Ready to run

npx skills add https://github.com/unclecatvn/agent-skills --skill odoo-code-tracer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: odoo-code-tracer
Source: https://github.com/unclecatvn/agent-skills/tree/main/agents/odoo-code-tracer
Command: npx skills add https://github.com/unclecatvn/agent-skills --skill odoo-code-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traces the full Odoo code execution path from an entry point to the end, enabling precise understanding of call sequences, overrides, and side effects.

Core Features & Use Cases

Entry-point discovery: identify controllers, cron jobs, server actions, and model methods.
Inheritance tracing: follow method overrides and super() calls across modules.
Visual and textual flow: generate a structured trace with file:line references and optional diagrams.
Use cases include code reviews, debugging complex workflows, and onboarding new developers by revealing execution paths.

Quick Start

Start tracing by loading an Odoo project and invoking the tracer on a chosen entry point or module to obtain a complete execution map.

Frequently Asked Questions about odoo-code-tracer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace an Odoo code execution path from an HTTP controller to its final output?▼

Trace Odoo code execution paths by identifying entry points like HTTP controllers and mapping the complete call sequence. This structured trace reveals method chains, decorator logic, and database interactions with file and line references.

How does inheritance and super() affect Odoo method overrides during a code trace?▼

Tracing inheritance in Odoo follows method overrides and super() calls across modules to reveal execution flow. It maps the complete call path to show overriding logic and downstream side effects from start to finish.

What is the best way to map side effects and database interactions in Odoo cron jobs?▼

Mapping side effects in Odoo cron jobs involves analyzing method chains and database interactions to produce a reproducible execution flow. The trace identifies the cron entry point and follows downstream effects to completion.

Can I trace server actions and model methods to understand downstream effects in an Odoo codebase?▼

Tracing server actions and model methods in an Odoo codebase maps the complete execution flow from start to finish. It analyzes method chains, decorators, and database interactions to reveal potential downstream effects.

Does this code tracing approach work for onboarding developers on complex Odoo workflows?▼

Code tracing for Odoo workflows supports developer onboarding by revealing complete execution paths and visual flows. It maps entry points, overrides, and side effects to clarify complex call sequences and method chains.

What are the limitations of tracing Odoo code flow when dealing with complex decorators?▼

Tracing Odoo code flow requires analyzing decorators, method chains, and database interactions to map execution paths. Limitations arise when dynamic dispatching obscures static call paths, complicating the reproducible execution flow.