odoo-commit

Generate and validate Odoo-style git commit messages with [TAG] headers.

1|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odoo-commit
Source: https://github.com/halim-23/odoo-dev-plugin/tree/main/skills/odoo-commit
Command: npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Odoo-style commit messages are essential for consistent collaboration and clear history in Odoo projects. This skill automates the creation and validation of commits that follow official guidelines.

Core Features & Use Cases

  • Enforces the [TAG] prefix format for commit headers and requires a WHY-focused description body.
  • Guides inclusion of related references (e.g., task numbers, issues) in the footer to improve traceability.
  • Prompts and validates the commit structure by running git diff --stat and git status before finalizing the commit.
  • Supports common tags like [FIX], [ADD], [REF], [IMP] to clearly express intent.

Quick Start

Prompt the assistant to generate a compliant Odoo commit message for your latest changes.

Frequently Asked Questions about odoo-commit

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

FAQPage Schema
How do I write an Odoo commit message that follows official guidelines?

To write an Odoo commit message, enforce a [TAG] prefix in the header, provide a WHY-focused body, and include related task references in the footer to ensure traceability.

What are the standard Odoo commit tags for git workflow?

Standard Odoo commit tags include [FIX] for bug fixes, [ADD] for new features, [REF] for refactoring, and [IMP] for improvements to clearly express the intent of your changes.

How do I validate my staged changes before committing in an Odoo project?

Validate staged changes for Odoo projects by running git diff --stat and git status to review what to commit, ensuring the commit structure is finalized before submission.

Why does my Odoo commit message need a WHY-focused body?

An Odoo commit message needs a WHY-focused body to maintain consistent collaboration and a clear project history, explaining the reasoning behind changes rather than just what changed.

Can I include task numbers and issue references in Odoo commit messages?

Yes, you can include related references like task numbers and issues in the footer of Odoo commit messages to improve project traceability and link changes to specific items.

What is the best way to automate Odoo-style commit message generation?

The best way to automate Odoo-style commit message generation is to use a skill that applies official guidelines, selects appropriate [TAG] prefixes, and checks git status before finalizing.