Menu
Make a commit in Git with an appropriate commit message for the currently staged changes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Run an iterative code review loop using Claude Code in non-interactive mode with Claude Fable 5 — Fable reviews the code and you apply fixes, repeating until Fable finds nothing more to fix. Use this skill whenever the user asks to "run a Fable review", "do a Fable code review loop", "let Claude review my code", "Fable로 코드 리뷰", "Claude로 코드 리뷰", "코드 리뷰 루프", or wants an independent Claude Fable 5 review of uncommitted changes or a branch followed by iterative fixes.
Run an iterative code review loop using the Codex MCP — Codex reviews the code and you apply fixes, repeating until Codex finds nothing more to fix. Use this skill whenever the user asks to "run a Codex review", "do a Codex code review loop", "let Codex review my code", "코드 리뷰 루프", "Codex로 코드 리뷰", or wants to review and iteratively fix uncommitted changes or a branch using the Codex AI agent.
Work through unresolved review comments on a GitHub pull request end-to-end — read each thread, fix the code where the reviewer is right, post a short reply explaining yourself where they aren't, group the fixes into well-scoped commits whose messages link to the comments they address, push, post follow-up replies naming the commit that resolved each thread (with bare commit hashes so GitHub auto-links them), resolve every triaged thread, and re-trigger Codex / Gemini if either bot reviewed the PR. Use this skill whenever the user asks to "address PR review", "handle review comments", "respond to review feedback", "apply review suggestions", "go through the review on PR
Basé sur la classification professionnelle SOC
| name | commit |
| description | Make a commit in Git with an appropriate commit message for the currently staged changes. |
| allowed-tools | Bash(git *) |
Please make a commit with an appropriate commit message for the currently staged changes.
Don't touch the staged changes, just create the commit.
The first line of the commit message should be a concise summary of the changes (50 characters or less). You shouldn't follow the conventional commits, in other words, just write a normal commit message without any special prefixes.
The second line of the commit message should be blank.
The rest of the commit message should provide more detailed explanations about the changes, wrapped at 72 characters.
If you have some references like issues or pull requests, you can add them in the body of the commit message, usually after a blank line. Issues and pull requests should be referenced as full URLs instead of #numbers, and you can put some verbs like "Fixes" or "Closes" before the URLs. For just references without any verbs, you can just put the URLs in the body.
When running git commit, pass the commit message via a HEREDOC to
preserve newlines correctly. Never use literal \n escape sequences
inside a quoted string, as they will appear as literal characters in
the commit message. For example:
git commit -m "$(cat <<'EOF'
Summary line here
Detailed explanation here.
EOF
)"
You don't have to format the commit message in Markdown, just write plain text. However, you can use some conventions that are commonly used in commit messages, such as using bullet points, numbered lists, or separating paragraphs with blank lines.
Don't put Generated with [Claude Code](https://claude.ai/code), or
Co-authored-by trailers at the end of the commit message. Instead,
use the Assisted-by trailer to indicate that the commit was generated by
an AI assistant, if necessary. The format of the Assisted-by trailer should
be:
Assisted-by: AGENT_NAME:MODEL_VERSION
For example:
Assisted-by: OpenCode:qwen3.6-plus
Assisted-by: Claude Code:claude-sonnet-4-6
Assisted-by: Gemini CLI:gemini-3.1-pro-preview
Assisted-by: Codex:gpt-5.5