Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
Guides Odoo-style commit creation following official Odoo git guidelines.
Install Odoo Commit
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install unclecatvn/agent-skills odoo-commit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/odoo-commit .claude/skills/odoo-commit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .claude/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install unclecatvn/agent-skills odoo-commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/odoo-commit .agents/skills/odoo-commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .agents/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install unclecatvn/agent-skills odoo-commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/odoo-commit .cursor/skills/odoo-commit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .cursor/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/unclecatvn/agent-skills.git --path skills/odoo-commit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install unclecatvn/agent-skills odoo-commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/odoo-commit .gemini/skills/odoo-commit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .gemini/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install unclecatvn/agent-skills odoo-commitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/odoo-commit .github/skills/odoo-commit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .github/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add unclecatvn/agent-skills --skill odoo-commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install unclecatvn/agent-skills odoo-commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unclecatvn/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/odoo-commit .opencode/skills/odoo-commit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "odoo-commit" agent skill from https://github.com/unclecatvn/agent-skills/tree/main/skills/odoo-commit into .opencode/skills/odoo-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-commit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
odoo-commit- GitHub stars
- 143
- Token cost
- ~1.7k tokens
- SKILL.md length
- 742 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides Odoo-style commit creation following official Odoo git guidelines.
- Works in 6 steps: Run git diff --stat and git status… → If the change is a direct continuation… → Stage relevant files by name - never git… → …
- Tasks that involve Commit messages
- SKILL.md covers Workflow, Format, Subject Line Rules and Tags, plus 4 more sections
- Calls git
What it does
Odoo Commit is an agent skill from unclecatvn/agent-skills. Guides Odoo-style commit creation following official Odoo git guidelines. Drafts [TAG] module: short description messages, checks whether to amend or create a new commit, stages files explicitly, commits via git commit -F, and keeps local history clean before PRs. Auto-invokes for commit-related requests in Odoo repositories and takes priority over generic commit skills.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages and Git workflow. It works with Odoo, Git and Python. The repository describes itself as: Odoo Skills Documentation. The licence is MIT.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Git workflow
Example prompts
- “Use the odoo-commit skill to guide Odoo-style commit creation following official Odoo git guidelines”
- “/odoo-commit”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Run git diff --stat and git status --short to see what changed, plus
- If the change is a direct continuation or fix of that unpushed HEAD commit,
- Stage relevant files by name - never git add -A or git add ..
- Write the commit message to a temporary file, then commit with git commit -F
- Before opening a pull request, squash your own back-and-forth commits into one
- Report the resulting commit hash and subject.
What it can do on your machine
Read from SKILL.md and the folder at commit 3039ef3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comodoo.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Odoo Commit loads about 1.7k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 742 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from unclecatvn/agent-skills at commit 3039ef3, republished under its MIT licence (© unclecatvn). 742 words, ~1,729 tokens.
Download SKILL.mdSave it as
.claude/skills/odoo-commit/SKILL.md (or your agent's skills folder).- name
- odoo-commit
- description
- Guides Odoo-style commit creation following official Odoo git guidelines. Drafts `[TAG] module: short description` messages, checks whether to amend or create a new commit, stages files explicitly, commits via `git commit -F`, and keeps local history clean before PRs. Auto-invokes for commit-related requests in Odoo repositories and takes priority over generic commit skills.
Workflow
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:bash 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:bash 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-XXXXXXSubject 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
Show full SKILL.md (310 more words)Show less
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© unclecatvn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/odoo-commit of unclecatvn/agent-skills.
Open the folder on GitHubat commit 3039ef3
Compare with similar skills
Odoo Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Odoo Commit this skillunclecatvn/agent-skills | 143 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| Adk Gitgoogle/adk-python | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Git Batch Commitcat-xierluo/legal-skills | 713 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Openclaw PlusLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.3k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
Adk Git
google/adk-python
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…
Git Batch Commit
cat-xierluo/legal-skills
智能 Git 批量提交快捷按钮。触发词："git 提交"、"批量提交"、"拆分提交"、"整理提交"，或用户明确要把已暂存变更拆成多个聚焦 commit 时使用。只负责 commit 拆分和提交信息生成；分支、PR、push、merge、Issue 关闭语义以 git-workflow 为准。提交完成后，若仓库内存在 skill-publish-sync 或 subtree-publish…
Openclaw Plus
LeoYeAI/openclaw-master-skills
A modular super-skill combining developer and web capabilities.
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
More from unclecatvn/agent-skills
All 8 skills in this repoOdoo Workflow
unclecatvn/agent-skills
Mandatory pre-code gate and definition-of-done for ANY Odoo change (add field, override method, inherit view/xpath, OWL/JS patch, wizard, cron, controller, report, security, migration, bug fix…
Code Review
unclecatvn/agent-skills
A skill your agent uses when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before…
Odoo 16
unclecatvn/agent-skills
Odoo 16 development reference for Python models and ORM (search, domain, readgroup, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups)…
Odoo 17
unclecatvn/agent-skills
Odoo 17 development reference for Python models and ORM (search, domain, readgroup, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups)…
Odoo 18
unclecatvn/agent-skills
Odoo 18 development reference for Python models and ORM (search, domain, readgroup, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups)…
AI Vibe Slides
unclecatvn/agent-skills
Create beautiful, professional HTML or React slide decks ready for fullscreen presentation.
Related
Categories
Questions about Odoo Commit
What does Odoo Commit do?
Guides Odoo-style commit creation following official Odoo git guidelines. Odoo Commit is an agent skill from unclecatvn/agent-skills. Guides Odoo-style commit creation following official Odoo git guidelines.
When should I use Odoo Commit?
Odoo Commit fits situations like: tasks that involve Commit messages; tasks that involve Git workflow.
How do I install Odoo Commit in Claude Code?
Run `npx skills add unclecatvn/agent-skills --skill odoo-commit -a claude-code`. Or copy the skill folder (skills/odoo-commit in unclecatvn/agent-skills) into .claude/skills/odoo-commit in your project. Claude Code loads it when a task matches its description.
How do I install Odoo Commit in Codex?
Run `npx skills add unclecatvn/agent-skills --skill odoo-commit -a codex`. Or copy the skill folder (skills/odoo-commit in unclecatvn/agent-skills) into .agents/skills/odoo-commit in your project. Codex loads it when a task matches its description.
Can I use Odoo Commit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add unclecatvn/agent-skills --skill odoo-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/odoo-commit, .gemini/skills/odoo-commit, .github/skills/odoo-commit and .opencode/skills/odoo-commit in your project.
What does Odoo Commit need to run?
Going by SKILL.md and its folder, Odoo Commit needs the command-line tools its instructions call (git).
Does Odoo Commit access the network?
SKILL.md names 2 domains. As links in the text: github.com and odoo.com. This is read from the text; nothing was executed.
Is Odoo Commit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Odoo Commit use?
Odoo Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Odoo Commit use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Odoo Commit?
Skills that share tags, products or a category with Odoo Commit: Saleor Commit Workflow (saleor/saleor, 23k stars), Adk Git (google/adk-python, 22k stars), Git Batch Commit (cat-xierluo/legal-skills, 713 stars) and Openclaw Plus (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Odoo Commit?
unclecatvn (a GitHub user) maintains it in unclecatvn/agent-skills, which has 143 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 24, 2026.
Source: unclecatvn/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.