odoo-commit skill
✓ VerifiedAutomates the creation of Odoo-style git commits following official guidelines for tags, subject lines, and message formatting.
- GitHub stars
- 151
- Files
- 1
- Last commit
- Oct 22, 2026
- License
- MIT
- Allowed tools
- —
What does the odoo-commit skill do?
odoo-commit automates the creation of Odoo-style git commits following official guidelines for tags, subject lines, and message formatting.
Summary generated from the skill's SKILL.md.
About the odoo-commit skill
Developers working on Odoo repositories can use this skill to automate the creation of git commits that strictly follow official Odoo guidelines. It manages the entire commit workflow by inspecting the current status with git diff and git status, determining whether to create a new commit or amend the previous unpushed HEAD commit to keep history clean. The tool ensures that files are staged individually rather than using bulk commands and uses a temporary file to execute the commit via the git commit -F command.
This skill prioritizes Odoo-specific formatting, including mandatory tags like [FIX], [IMP], or [REF], and specific subject line structures such as [TAG] module: description. It enforces rules like the imperative mood, a 72-character ceiling for headers, and the exclusion of AI attribution or redundant descriptions of what the code does. By handling the technicalities of message drafting and history management, it helps maintain a professional, standardized repository history suitable for pull requests.
What an agent can do with it
- 1Drafting standardized Odoo commitsAn AI agent can generate a correctly formatted commit message with the appropriate tag and module name based on current changes.
- 2Ensuring subject line complianceThe tool validates that the commit header functions as a valid sentence when preceded by the phrase 'if applied, this commit will'.
- 3Managing unpushed changesThe agent can decide to amend the last local commit instead of creating a new one if the current changes are a direct continuation.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the odoo-commit skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the odoo-commit skill in Plugin
/plugin marketplace add unclecatvn/agent-skills /plugin install agent-skills@unclecat-agent-skills
Install the odoo-commit skill in Claude Code
~/.claude/skills/odoo-commit/SKILL.md
$ npx degit unclecatvn/agent-skills/skills/odoo-commit ~/.claude/skills/odoo-commitInstall the odoo-commit skill in Claude Code (project)
.claude/skills/odoo-commit/SKILL.md
$ npx degit unclecatvn/agent-skills/skills/odoo-commit .claude/skills/odoo-commitInstall the odoo-commit skill in Codex
~/.agents/skills/odoo-commit/SKILL.md
$ npx degit unclecatvn/agent-skills/skills/odoo-commit ~/.agents/skills/odoo-commitInstall the odoo-commit skill in Gemini CLI
~/.gemini/skills/odoo-commit/SKILL.md
$ npx degit unclecatvn/agent-skills/skills/odoo-commit ~/.gemini/skills/odoo-commitInstall the odoo-commit skill in Claude.ai
npx degit unclecatvn/agent-skills/skills/odoo-commit odoo-commit && zip -r odoo-commit.zip odoo-commit # claude.ai → Customize → Skills → + → Create skill → Upload a skill → odoo-commit.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachableunclecatvn/agent-skills/skills/odoo-commit is public and reachablegithub.com/unclecatvn/agent-skills/tree/HEAD/skills/odoo-com ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-22github.com/unclecatvn/agent-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/unclecatvn/agent-skills/blob/HEAD/skills/odoo-com ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/unclecatvn/agent-skills/blob/HEAD/skills/odoo-com ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/unclecatvn/agent-skills/blob/HEAD/skills/odoo-com ↗Finding
SKILL.md
View on GitHubWorkflow
-
Run
git diff --statandgit status --shortto see what changed, plusgit log -1 --oneline(andgit log @{u}.. --onelineif a remote-tracking branch exists) to see the last local commit and whether it's still unpushed. -
If the change is a direct continuation or fix of that unpushed
HEADcommit, skip drafting a new message and fold it in instead of creating a second commit for the same logical change:git add <file> git commit --amend --no-edit # or drop --no-edit to also revise the messageOtherwise, draft a new commit message.
-
Stage relevant files by name - never
git add -Aorgit add .. -
Write the commit message to a temporary file, then commit with
git commit -F:
cat > /tmp/odoo-commit-message.txt <<'EOF'
[TAG] module: short description
Optional body line.
EOF
git commit -F /tmp/odoo-commit-message.txt
Any equivalent temp-file flow is fine (for example, using PowerShell's
Set-Content or another editor) as long as the final commit is created with
git commit -F <file>.
-
Before opening a pull request, squash your own back-and-forth commits into one clean commit per logical change (per OCA guidelines): the rest of the world doesn't need your intermediate "fix bug 1", "fix bug 2" history - only the final state and a clear summary. For a single trailing fix,
git commit --amend(step 2) is usually enough; for folding several commits into one, use an interactive rebase instead:git rebase -i HEAD~N # N = number of commits to foldKeep the first line as
pickwith the real[TAG] module: descriptionmessage, mark the restfixup(drop their messages) orsquash(merge messages):pick 1949129 [IMP] module: Introduce feature A fixup d2cf643 Fix bug 1 of feature A fixup 42bd9e8 Fix bug 2 of feature A fixup 7f767d5 Fix bug 3 of feature AEither way, only rewrite commits that are still local/unpushed, or on a branch you alone own - never amend or rebase shared history without confirming with the user first.
-
Report the resulting commit hash and subject.
Do not bypass pre-commit hooks. If a hook fails, fix the issue, re-stage the changes, and create the commit again.
Format
[TAG] module: short description
Optional body explaining WHY, not what. What is visible in the diff.
Focus on motivation, constraints, and decisions made.
task-XXXX, opw-XXXXXX
Subject Line Rules
[TAG] module: description- tag in brackets, then module name, colon, space, description- Target the whole header (
[TAG] module: description) at about 50 characters for readability; 72 is a hard ceiling, not something to aim for - Self-test: the header must read as a valid sentence after "if applied, this commit
will
<header>" - e.g.[IMP] base: prevent to archive users linked to active partners-> "if applied, this commit will prevent to archive users linked to active partners" - Never use single, vague words like "bugfix" or "improvements" as the description - it must be self-explanatory and state the reason for the change
- Imperative mood: "add", "fix", "remove" - not "added", "fixes"
- No trailing period
- Module = technical module name (e.g.
hhc,plc,nhso_stddataset,imc) - Avoid touching multiple modules in one commit - split per module so each can be
reverted independently. If truly unavoidable, list the modules or use
various
Tags
[FIX]- bug fix; used in stable versions, also valid for recent dev bugs[REF]- refactoring: feature heavily rewritten[ADD]- adding new modules[REM]- removing resources: dead code, views, modules[REV]- reverting commits[MOV]- moving files (no content change; use git mv)[REL]- release commits: major/minor stable versions[IMP]- improvements: most incremental dev changes[MERGE]- merge commits / forward port of bug fixes[CLA]- signing Odoo Individual Contributor License[I18N]- translation file changes[PERF]- performance patches[CLN]- code cleanup[LINT]- linting passes
Body Rules
- Skip body when subject is self-explanatory
- Include body for: non-obvious WHY, breaking changes, migration notes, task references
- Explain WHY, not WHAT - the diff already shows what changed. WHAT is only worth spelling out when a technical choice or trade-off was involved, and then explain WHY that choice was made
- Don't force brevity for its own sake: official Odoo guidance explicitly says not to hesitate being verbose when the reasoning deserves it. Every line should still earn its place - no restating the diff, no filler
- Wrap at 72 characters per line
- Reference task IDs at the end:
task-XXXX,opw-XXXXXX,Fixes #123,Closes #123
What Never Goes In
- "This commit does X" - the diff says what
- "I", "we", "now", "currently"
- AI attribution of any kind:
Co-Authored-By: Claude ...trailers,Generated with Claude Codelines, session links. If the tooling injects one, remove it before committing - Restating the file name or module when the subject already says it
Pull Requests
- Title = the commit header (
[TAG] module: description); one logical change per PR - Body explains WHY and how it was verified (test command, screenshots for views); the diff shows WHAT
- No AI attribution anywhere in the body: no "Generated with" footer, no
Co-Authored-By, no session links - Do not add or edit author/reviewer lines; git already records the author
Examples
Examples from the official Odoo git guidelines:
[REF] models: use `parent_path` to implement parent_store
This replaces the former modified preorder tree traversal (MPTT) with the
fields `parent_left`/`parent_right`[...]
[FIX] account: remove frenglish
[...]
Closes #22793
Fixes #22769
[FIX] website: remove unused alert div, fixes look of input-group-btn
Bootstrap's CSS depends on the input-group-btn element being the first/last
child of its parent. This was not the case because of the invisible and
useless alert.
Header-only, illustrating the "valid sentence" self-test:
[IMP] base: prevent to archive users linked to active partners
Files in this skill
1odoo-commit skill questions
How do I install the odoo-commit skill in Claude Code?
Run npx degit unclecatvn/agent-skills/skills/odoo-commit ~/.claude/skills/odoo-commit. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the odoo-commit skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should Odoo commit messages be formatted?
Messages should follow the format [TAG] module: short description with an optional body explaining the 'why' rather than the 'what'.
What are the rules for the commit subject line?
The subject line should be in the imperative mood (e.g., 'add', 'fix'), avoid trailing periods, and should read as a valid sentence when preceded by 'if applied, this commit will'.
Should I include AI attribution in my commits?
No, you must never include AI attribution such as 'Co-Authored-By' or 'Generated with Claude' in the commit message.
How should I handle multiple commits before a pull request?
You should squash your intermediate commits into a single clean commit per logical change using interactive rebase.