Menu
Defines the standard format and rules for git commit messages in this project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit_standard |
| description | Defines the standard format and rules for git commit messages in this project. |
This project uses a standardized git commit message format based on Conventional Commits, with an added touch of our project's specific context.
<type>(<scope>): <subject>
<body>
<footer>
Must be one of the following:
feat: A new feature (e.g., adding a new user profile section)fix: A bug fix (e.g., fixing tooltip text)docs: Documentation only changes (e.g., updating README or dictionaries)style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries such as documentation generationIndicates the area of the codebase the commit affects. Common scopes in this project:
dashboard: Admin/User dashboard UI or logiccomponents: Reusable UI elementsutils: Shared utility functionsauth: Authentication flowspayment: Payment and webhook integrationsi18n: Dictionaries and localizationfeat(auth): add OAuth login support
Implement Google and GitHub OAuth providers for faster
user onboarding and integrate them into the login screen.
When you are asked to commit changes, ALWAYS reference this skill and follow the format precisely. If committing multiple diverse changes, try to group them logically or use feat(core) / chore(all) if they span the entire project.
CRITICAL RULE FOR AI AGENTS (Jules):
All commit subjects and bodies MUST be written in Japanese (日本語), regardless of the prompt language. The <type>(<scope>) prefix remains in English.
Example: feat(auth): Googleログインを追加
feat/<short-description> — 新機能fix/<short-description> — バグ修正refactor/<short-description> — リファクタリングdocs/<short-description> — ドキュメント変更.ts, .tsx, .css, .json 等）は必ず feature ブランチで作業するmain への直接 push はドキュメントのみの変更に限定する
blueprint.md, AGENTS.md, GEMINI.md, .agents/skills/*.mdlib/, app/, components/, __tests__/ 配下の変更AI開発チームの役割定義。各エージェントの責務・行動指針・実行ステップを規定する。
AI同士のバトンタッチ（タスク委譲）とチェック体制。セッション開始時のPR確認から終了時のIssue作成までのルールを定義する。
バグ修正時のリグレッションテスト作成義務と、グローバル状態共有の禁止ルール。
コーディング規約。ESLint/TypeScript/React/Next.jsの品質基準と、AIエージェントがコミット前に守るべきルールを定義する。
README.mdとblueprint.mdの役割分担と更新義務を定義するドキュメント管理ポリシー。
ロジックの変更とUIの変更に対するテスト戦略と基準を定義する。