メニュー
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Self-improve AI Factory skills based on project context, accumulated patches, and codebase patterns. Analyzes what went wrong, what works, and enhances skills to prevent future issues. Use when you want to make AI smarter for your project.
Add project-specific rules and conventions to the configured RULES.md artifact. Each invocation appends new rules. These rules are automatically loaded by /aif-implement before execution. Use when user says "add rule", "remember this", "convention", or "always do X".
Go idioms, code conventions, and best practices tailored for the WGTray codebase. Covers error handling, concurrency (sync.RWMutex, goroutines), platform-specific file split patterns, systray UI patterns, and macOS admin execution. Use when writing, reviewing, or refactoring any Go code in this project.
Generate architecture guidelines for the project. Analyzes tech stack from DESCRIPTION.md, recommends an architecture pattern, and creates .ai-factory/ARCHITECTURE.md. Use when setting up project architecture, asking "which architecture", or after /aif setup.
Analyze project and generate or enhance build automation file (Makefile, Taskfile.yml, Justfile, Magefile.go). If a build file already exists, improves it by adding missing targets and best practices. Use when user says "generate makefile", "create taskfile", "add justfile", "setup mage", or "build automation".
Analyze project and generate Docker configuration: Dockerfile (multi-stage dev/prod), compose.yml, compose.override.yml (dev), compose.production.yml (hardened), and .dockerignore. Includes production security audit. Use when user says "dockerize", "add docker", "docker compose", "containerize", or "setup docker".
| name | aif-commit |
| description | Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit". |
| argument-hint | [scope or context] |
| allowed-tools | Read Bash(git *) AskUserQuestion Questions |
| disable-model-invocation | false |
Generate commit messages following the Conventional Commits specification.
FIRST: Read .ai-factory/config.yaml if it exists to resolve:
paths.description, paths.architecture, paths.rules_file, paths.roadmap, and paths.ruleslanguage.ui for prompts and commit message conventionsgit.skip_push_after_commit for post-commit push behaviorrules.base plus any named rules.<area> entriesIf config.yaml doesn't exist, use defaults:
.ai-factory/ for all artifactsen (English)skip_push_after_commit: falseRead .ai-factory/skill-context/aif-commit/SKILL.md — MANDATORY if the file exists.
This file contains project-specific rules accumulated by /aif-evolve from patches,
codebase conventions, and tech-stack analysis. These rules are tailored to the current project.
How to apply skill-context rules:
Enforcement: After generating any output artifact, verify it against all skill-context rules. If any rule is violated — fix the output before presenting it to the user.
Analyze Changes
git status to see staged filesgit diff --cached to see staged changesRun Context Gates (Read-Only)
paths.rules_file + rules.base + named rules.<area>) for commit conventionsROADMAP.md, RULES.md) are WARN, not blockersDetermine Commit Type
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Code style (formatting, semicolons)refactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementtest: Adding or modifying testsbuild: Build system or dependenciesci: CI configurationchore: Maintenance tasksIdentify Scope
src/auth/ → auth)Generate Message
<type>(<scope>): <subject>
<body>
<footer>
Simple feature:
feat(auth): add password reset functionality
Bug fix with body:
fix(api): handle null response from payment gateway
The payment API can return null when the gateway times out.
Added null check and retry logic.
Fixes #123
Breaking change:
feat(api)!: change response format for user endpoint
BREAKING CHANGE: user endpoint now returns nested profile object
When invoked:
Check for staged changes
Analyze the diff content
Run read-only context gates and summarize findings as WARN/ERROR
If commit type is feat/fix/perf and roadmap exists, check milestone linkage; if missing, warn and suggest adding linkage in commit body/footer
Propose a commit message
Confirm with the user before committing:
AskUserQuestion: Proposed commit message:
<type>(<scope>): <subject>
Options:
1. Commit as is
2. Edit message
3. Cancel
Handle user response:
AskUserQuestion, then return to step 6 with the new messageExecute git commit with the confirmed message
Post-commit push handling:
If git.skip_push_after_commit = true in resolved config:
Otherwise (default behavior), offer to push:
git status -sbgit push -u origin <branch>git pushAskUserQuestion: Push to remote?
Options:
1. Push now
2. Skip push
git push -u origin <branch>git pushIf argument provided (e.g., /aif-commit auth):
/aif-commit has no implicit strict mode — context gates are warning-first unless user explicitly requests blocking behaviorShow which files/hunks belong to which commit
Confirm split plan with the user:
AskUserQuestion: Split into separate commits?
Options:
1. Yes, split as suggested
2. No, commit everything together
3. Let me adjust the grouping
Handle user response:
AskUserQuestion, then return to step 2 with the new planUnstage all: git reset HEAD
Stage and commit each group separately using git add <files> + git commit
Offer to push only after all commits are done
Co-Authored-By or any other trailer attributing authorship to the AI. Commits must not contain AI co-author lines