commit
npx machina-cli add skill iktakahiro/python-fastapi-ddd-skill/commit --openclawCommit
Communication
- Communicate with the developer in Japanese.
- Write code comments and commit messages in English.
Commit message
Follow Conventional Commits: https://www.conventionalcommits.org/en/v1.0.0/
<type>[optional scope]: <description>
[optional body]
Use these types:
- fix
- feat
- chore
- docs
- refactor
- test
Use scope when clear (directory name or skill name). Examples:
- docs(python-fastapi-ddd-skill): expand DDD reference notes
- chore(codex): adjust local SKILL instructions
Commit workflow
- Review changes with
git statusandgit diff. - This repo has no mandatory pre-commit command; do not run Node/bun/turbo checks.
- If the user explicitly asks to commit everything (e.g., "全体", "全部", "commit all"), include all working tree changes without asking for confirmation.
- Otherwise, do not ask about unrelated changes. Leave unrelated files untouched and stage only the files relevant to the task.
- Do not bundle all task changes into a single commit. Split commits by logical change units and scope/intent (e.g., README updates vs feature changes).
- Commit directly without extra confirmation.
- After committing, report a brief summary of created commits.
- Push only when the user asks.
- Do not amend commits unless the user asks.
Allowed dot directories
.claude.codex.cursor.vscode.kiro
Source
git clone https://github.com/iktakahiro/python-fastapi-ddd-skill/blob/main/.codex/skills/commit/SKILL.mdView on GitHub Overview
Prepare and create git commits in this repository using Conventional Commits to ensure clear, scoped history. This skill guides you through message formatting, file scoping, and logical commit splitting when task changes are requested.
How This Skill Works
Messages must be in English and follow the scheme <type>[optional scope]: <description> with types like fix, feat, chore, docs, refactor, test. Communicate with the developer in Japanese, and note that commit messages should reflect task scope accurately. The repo has no mandatory pre-commit checks, so you can commit directly; after committing, provide a brief summary of created commits.
When to Use It
- You are asked to commit or split a task into logical changes.
- You need to create a feature or bugfix commit following Conventional Commits.
- You want to stage only files relevant to the task to avoid unrelated changes.
- You want to include a clear scope (directory name or skill name) in the commit.
- You want a brief summary after committing and to decide whether to push later.
Quick Start
- Step 1: Review changes with git status and git diff to understand scope.
- Step 2: Stage relevant files (git add <files>) and craft a message like <type>[optional scope]: <description>.
- Step 3: Run git commit -m "<type>[optional scope]: <description>" and report a brief summary of created commits.
Best Practices
- Follow the Conventional Commits pattern: <type>[optional scope]: <description>.
- Use a descriptive English description and include scope when clear.
- Split large tasks into multiple commits by logical change units.
- Stage only the files related to the current task; avoid bundling unrelated changes.
- Review changes with git status and git diff before committing.
Example Use Cases
- feat(python-fastapi-ddd-skill): add commit workflow guide
- fix(commit): correct message formatting example
- docs(commit): update conventional commits reference
- chore(codex): adjust local SKILL instructions
- refactor(commit): reorganize commit workflow steps for clarity
