القائمة
Generate an English git commit message from the current repository changes, copy it to the clipboard, and optionally save it to a file.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a Chinese git commit message from the current repository changes, copy it to the clipboard, and optionally save it to a file.
Generate an English git commit message from the current repository changes. Use this when the user invokes /commit_en or asks for an English commit message.
Generate a Chinese git commit message from the current repository changes. Use this when the user invokes /commit_zh or asks for a Chinese commit message.
| name | commit_en_copy |
| description | Generate an English git commit message from the current repository changes, copy it to the clipboard, and optionally save it to a file. |
| allowed-tools | bash |
When the user enters /commit_en_copy, or asks for an English git commit message that should also be copied to the clipboard, follow these rules strictly.
You are a rigorous version control assistant. Based on the complete file changes in the current repository and the real diff contents, generate only one complete commit message that can be used directly with git commit -m.
git commit, git add, git reset, git checkout, git restore, or any other command that changes repository state.git -P diff HEAD; using git diff HEAD is strictly forbidden./commit_en_copy, treat it as an output path or output directory.First confirm that the current directory is a Git repository.
Run git status --short --untracked-files=all and parse every status line, including A, M, D, R, C, U, ??, and related combinations.
Run git -P diff HEAD and use it as the primary source of truth for tracked changes.
If git status --short --untracked-files=all contains ??, you may inspect those untracked files in read-only mode to complete the per-file notes, but you must still execute git -P diff HEAD first.
Determine the core intent by combining change proportion and business-value priority, in this order: feature > fix > refactor > config > docs > style > build > git.
Select exactly one prefix from: feat:, fix:, refactor:, docs:, style:, config:, build:, git:. If none fit, use another official Conventional Commits prefix such as perf:, test:, or chore:.
The first line must follow this format: prefix: one-sentence core summary
The first line must be no longer than 80 characters, and it must not end with a period.
After one blank line, add summary bullets using -:
After another blank line, add file-by-file change notes for every file listed in git status, using one of these exact formats:
- **New file** path: description
- **Deleted** path: description
- **Modified** path: description
- **Renamed** old-path → new-path: description
Per-file notes must follow these rules:
Parse optional invocation arguments:
/commit_en_copy: copy the raw commit message to the clipboard and output it directly/commit_en_copy ./commit.txt: copy the raw commit message to the clipboard and write it to ./commit.txt/commit_en_copy ~/Desktop/Commit.md: copy the raw commit message to the clipboard and write it to the provided file path/commit_en_copy ~/: copy the raw commit message to the clipboard and write it into that directory using ${project_name}_commit_message.txtAfter generating the final commit message, you must call copy_commit_message.sh from this skill directory:
/, the default filename is ${project_name}_commit_message.txtIf clipboard copy fails, output a concise error instead of pretending it succeeded.
The final answer must be the raw commit message only, with no code fences, explanation, heading, preface, path notice, or trailing note.
chore: no changes to commitgit status --short --untracked-files=all