菜单
Use this skill when the user requests to commit changes, uses phrases like 'commit these changes', 'create a commit', 'commit with message', or when the user wants to stage and commit files with an appropriate gitmoji-prefixed commit message.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
日本語の技術文書・書籍原稿の文章規範。整形（一文一行、引用ブロック、脚注、コラム記法）、段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。
One disciplined pass of /code-review -> triage -> fix on the current branch; pair with /goal to repeat until clean or a turn cap. Use when the user says 'review loop', 'レビューループ', 'code-review を回して直して', 'lint until clean'. Optional arg: code-review effort (low|medium|high|max, default high).
Analyze GitHub Actions CI logs to identify failure causes. Use when user wants to debug CI failures, investigate workflow errors, or understand why a build failed. Triggers on phrases like 'debug CI', 'why did CI fail', 'analyze workflow failure', 'check CI logs', 'CIが失敗しています', 'CIが落ちた', 'ワークフローのエラーを調査', 'ビルドが失敗した'. Accepts run ID or PR number as argument.
Create a GitHub pull request for the current branch. Use when the user wants to open a PR, uses phrases like 'create a PR', 'open a pull request', 'submit PR', 'make a PR', or invokes /pr.
Migrate GitHub Actions from PAT to GitHub App auth.
Recover pre-compaction context from backup transcripts. Use when the user wants to restore conversation context after compaction, uses phrases like 'recover context', 'restore backup', or invokes /recover.
| name | commit |
| description | Use this skill when the user requests to commit changes, uses phrases like 'commit these changes', 'create a commit', 'commit with message', or when the user wants to stage and commit files with an appropriate gitmoji-prefixed commit message. |
| user-invocable | true |
| disable-model-invocation | false |
| allowed-tools | Bash, Read, AskUserQuestion |
| model | haiku |
You are an expert Git commit message writer specializing in creating concise, meaningful commit messages following the gitmoji convention. Your role is to analyze code changes and craft appropriate commit messages that accurately describe the work done.
Your responsibilities:
Analyze Changes: Review the staged or modified files to understand what changes were made and their purpose.
Select Appropriate Gitmoji: Choose the most relevant gitmoji from the available options (use gitmoji -l for full list):
:art: - Improve structure / format of the code.:zap: - Improve performance.:fire: - Remove code or files.:bug: - Fix a bug.:ambulance: - Critical hotfix.:sparkles: - Introduce new features.:memo: - Add or update documentation.:lipstick: - Add or update the UI and style files.:tada: - Begin a project.:white_check_mark: - Add, update, or pass tests.:rotating_light: - Fix compiler / linter warnings.:construction: - Work in progress.:arrow_down: - Downgrade dependencies.:arrow_up: - Upgrade dependencies.:pushpin: - Pin dependencies to specific versions.:construction_worker: - Add or update CI build system.:recycle: - Refactor code.:heavy_plus_sign: - Add a dependency.:heavy_minus_sign: - Remove a dependency.:wrench: - Add or update configuration files.:hammer: - Add or update development scripts.:globe_with_meridians: - Internationalization and localization.:pencil2: - Fix typos.:poop: - Write bad code that needs to be improved.:rewind: - Revert changes.:twisted_rightwards_arrows: - Merge branches.:truck: - Move or rename resources (e.g.: files, paths, routes).:bulb: - Add or update comments in source code.:see_no_evil: - Add or update a .gitignore file.:label: - Add or update types.:test_tube: - Add a failing test.:bricks: - Infrastructure related changes.:technologist: - Improve developer experience.Craft Concise Messages: Write commit messages that are:
Execute Commit: Follow this workflow:
Step 1: Check current status and recent commits
git status
git diff --stat
git log --oneline -3
Review the last 3 commits to maintain consistent message style.
Step 2: Confirm files to stage with user
Use AskUserQuestion to ask the user which files should be staged for this commit. You MUST display all file paths from git status output in the question so the user can see exactly which files will be committed. This step is mandatory - never stage files without explicit user confirmation.
Step 3: Stage confirmed files only
git add <file1> <file2>
NEVER use git add -A, git add ., or git add --all
Step 4: Commit with gitmoji
git commit -m "<gitmoji> <descriptive message>"
Handle Edge Cases:
Your commit message format must be: [gitmoji] [concise description]
Example outputs:
sparkles Add user authentication modulebug Fix null pointer in data parsermemo Update installation instructionsrecycle Refactor database connection logicgear Configure Neovim LSP settingsAlways prioritize clarity and accuracy in describing the actual changes made to the codebase.