odoo-bug-verify

odoo-bug-verify is a command for Claude Code from stanleykao72/claude-code-spec-workflow-odoo. It costs 0 tokens per session (2,682 once invoked), scanned A, original, MIT.

An Odoo bug-fix verification command for Odoo, a business-management system with modules such as inventory, sales, and human resources. It checks whether a repaired module works with the rest of the ERP system.

In plain words
What is it for?
Use it to verify bugs involving inventory, discounts, attendance, and other Odoo modules. It loads the bug report, root-cause analysis, and fix details before testing.
Why use it?
It helps catch fixes that appear correct in isolation but break business processes or other Odoo modules. It also checks that previously working behavior has not regressed.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to verify bugs involving inventory, discounts, attendance, and other Odoo modules. It loads the bug report, root-cause analysis, and fix details before testing.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-verify
Install

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.

Clone the repo
git clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odoo

Made for: Claude Code.

Wrote 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.

agentmods badge for odoo-bug-verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-verify.svg)](https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-verify)
Your own site
<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-verify"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-bug-verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,682 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02682
Opus 5 $0.00000 $0.01341
Sonnet 5 $0.00000 $0.00536
Haiku 4.5 $0.00000 $0.00268

Measured 8d ago against content hash 7057fc9adfce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

odoo-bug-verify 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.

src/markdown/commands/odoo-bug-verify.md · 372 lines

How it starts

The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.

odoo-bug-verify - Verify Odoo Module Bug Fix

Verify and validate that an Odoo module bug fix is working correctly with comprehensive ERP integration testing.

Usage

/odoo-bug-verify [module-bug-name]

Examples:

/odoo-bug-verify inventory-negative-stock
/odoo-bug-verify sale-discount-calculation  
/odoo-bug-verify hr-attendance-timeout

What This Command Does

This command performs comprehensive verification of Odoo module bug fixes, including module integration testing, business process validation, and ERP-specific regression testing.

Instructions

Use the @odoo-spec-task-executor agent to verify Odoo module bug fixes:


Perform comprehensive Odoo module bug fix verification with ERP integration testing:

# 1. Prerequisites and Context Loading
Load complete verification context:

## Bug Context
- Load existing bug documentation from [module-path]/.spec/bugs/[bug-name]/
  * report.md: Original bug report and symptoms
  * analysis.md: Root cause analysis and solution plan
  * fix.md: Implementation details and changes made

## Module Context  
- Load target module configuration and dependencies
- Load module manifest (__manifest__.py) for version compatibility
- Understand module's integration points and dependencies

## Odoo Project Context
- Load .odoo-dev/steering/ documents for standards compliance
- Load module development standards and testing guidelines
- Understand business process integration requirements

# 2. Odoo-Specific Verification Framework

## Module Integration Verification
Comprehensive ERP integration testing:

### Model Integration Testing
- **Database Consistency**: Verify schema changes are applied correctly
- **ORM Functionality**: Test model methods and computed fields
- **Inheritance Chains**: Validate _inherit and _inherits relationships work correctly
- **Constraint Validation**: Check database constraints and Python constraints
- **Record Rules**: Verify security rules function correctly

### View Integration Testing
- **Template Rendering**: Confirm views render without errors
- **JavaScript Integration**: Test client-side functionality
- **Widget Behavior**: Validate custom widgets and form elements
- **Access Control**: Verify view-level security restrictions

### Business Logic Verification
- **Workflow Integration**: Test state transitions and approvals
- **Compute Methods**: Validate field calculations and dependencies
- **Onchange Methods**: Test real-time field updates
- **Action Methods**: Verify button actions and server actions

## ERP Process Integration Testing

### Multi-Module Integration
Test interaction with dependent modules:
- **Data Flow**: Verify data flows correctly between modules
- **API Integration**: Test internal API calls and web controllers
- **Event Handling**: Validate signal/event handling between modules
- **Transaction Integrity**: Ensure transaction boundaries are respected

### Business Process Validation
Test end-to-end business processes:
- **User Workflows**: Test complete user interaction scenarios  
- **Automated Processes**: Validate scheduled actions and cron jobs
- **Reporting Integration**: Verify report generation and data accuracy
- **External Integration**: Test third-party system integration

### Multi-Tenancy Testing
Odoo-specific multi-company validation:
- **Company Isolation**: Verify data isolation between companies
- **Security Context**: Test company-specific access rules
- **Localization**: Validate currency and language handling
- **Configuration**: Test company-specific settings

# 3. Regression Testing Strategy

## Module Regression Testing
Prevent regression in existing functionality:
- **Existing Features**: Test all module features still work
- **Performance Impact**: Measure performance before/after fix
- **Memory Usage**: Check for memory leaks or excessive usage
- **Database Impact**: Validate query performance and indexing

## Integration Regression Testing
Ensure other modules still function:
- **Dependent Modules**: Test modules that depend on this module
- **Core Integration**: Verify core Odoo functionality unaffected
- **Third-party Modules**: Test community/enterprise module compatibility

# 4. Test Execution and Documentation

## Test Case Execution
Execute comprehensive test scenarios:

### Automated Testing
- **Unit Tests**: Run pytest-odoo unit tests for the module
- **Integration Tests**: Execute inter-module integration tests
- **Performance Tests**: Run load testing scenarios
- **Regression Tests**: Execute existing test suites

### Manual Testing
- **User Acceptance**: Test from end-user perspective
- **Edge Cases**: Test boundary conditions and error scenarios
- **Browser Testing**: Test in different browsers if web-related
- **Mobile Testing**: Test responsive design if applicable

## Verification Documentation
Create comprehensive verification report in [module-path]/.spec/bugs/[bug-name]/verification.md:

Read the full file on GitHub · 372 lines

Changes

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.

  1. 8d ago First seen · 372 lines · 0 tokens per session scan A 7057fc9adfce

Subscribe to this mod's changes

odoo-bug-verify 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 2,682 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.