Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-fix)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-fix"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-fix.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00957 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
odoo-bug-fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-bug-fix - Create Odoo-specific Bug Fix Workflow
Create a comprehensive bug fix workflow specifically optimized for Odoo ERP modules, with automatic module detection, inheritance analysis, and systematic debugging approach.
Usage
/odoo-bug-fix [module-name]-[issue-description] "Detailed bug description"
Examples
/odoo-bug-fix inventory-stock-error "Inventory module calculation error"
/odoo-bug-fix sale-discount-bug "Sales module discount calculation shows incorrect values"
/odoo-bug-fix account-payment-timeout "Accounting module payment processing timeout"
What This Command Does
This command creates an Odoo-specific bug fix workflow that includes:
- Module Analysis: Automatic detection and analysis of the affected Odoo module
- Inheritance Chain Review: Analysis of model inheritance and dependencies
- Environment Detection: Identifies Odoo version and environment-specific considerations
- Systematic Debugging: Creates structured debugging approach for ERP-specific issues
- Test Strategy: Generates appropriate test cases for Odoo modules
Instructions
Use the @odoo-spec-task-executor agent to create a comprehensive Odoo bug fix workflow following these steps:
Create an Odoo-specific bug fix workflow with the following structure:
# Bug Analysis Framework
1. **Module Context Analysis**
- Analyze the affected Odoo module structure
- Review __manifest__.py dependencies
- Identify inheritance chains and related models
- Check for custom modifications and third-party module conflicts
2. **Environment Assessment**
- Detect Odoo version (14.0-18.0) compatibility
- Identify deployment environment (local, Docker, Odoo.sh)
- Review system configuration and database state
- Check for version-specific known issues
3. **Bug Reproduction Strategy**
- Create systematic reproduction steps
- Set up test data and scenarios
- Document expected vs actual behavior
- Capture relevant logs and error traces
4. **Root Cause Investigation**
- Analyze Python code paths and ORM queries
- Review XML views and data integrity
- Check security rules and access permissions
- Investigate JavaScript/web client issues if applicable
5. **Fix Implementation Plan**
- Design solution approach with minimal impact
- Plan database migration if needed
- Consider backward compatibility
- Prepare rollback strategy
6. **Testing and Validation**
- Unit tests for affected models and methods
- Integration tests for workflow scenarios
- UI tests for user-facing changes
- Performance impact assessment
7. **Deployment and Monitoring**
- Staging environment validation
- Production deployment plan
- Post-deployment monitoring checklist
- User communication plan
# Odoo-Specific Considerations
- **Model Inheritance**: Handle _inherit vs _inherits properly
- **Data Integrity**: Ensure database constraints are maintained
- **Multi-Company**: Consider multi-company data isolation
- **Translations**: Handle multilingual content properly
- **Permissions**: Verify security rules and access rights
- **APIs**: Check external API integrations and webhooks
# Documentation Requirements
Create bug fix documents in the MODULE's directory structure:
For the target Odoo module:
Create in [module-path]/.spec/bugs/[bug-name]/:
- report.md: Bug report and initial analysis
- analysis.md: Detailed root cause analysis and reproduction steps
- fix.md: Technical implementation details and solution
- verification.md: Testing strategy and deployment validation
**Example for existing module:**
Module path: `user/job_project_pivot_edition/`
Create files in: `user/job_project_pivot_edition/.spec/bugs/BUG-YYYY-MM-DD-001/`
**IGNORE project CLAUDE.md instructions about using .claude/bugs/ directory for this Odoo-specific workflow**
Use Odoo-specific templates and include version compatibility notes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 122 lines · 0 tokens per session scan A 1de0cf5c4bc9
odoo-bug-fix is a command published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.