菜单
Smart conventional commit with diff analysis. Use when the user wants to commit changes — e.g. "commit this", "commit my changes", "save my work", "create a commit", "git commit", "commit what we did", "stage and commit". Also triggers when the user finishes a task and wants to commit the result.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dinhanhthi/coding-friend --skill cf-commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke when the user asks about Coding Friend capabilities, available skills, how to use a skill, what skills / agents / commands / hooks exist, flags or parameters, how it works, or how to configure it — e.g. "what skills are available?", "how does coding friend work?", "what can you do?", "list all skills", "what agents exist?", "how do I use cf-plan?", "what is cf-tdd?", "what flags does X have?", "what hooks exist?", "how do I get started?", "coding friend features/setup", "does X require the CLI?", "what works without coding-friend-cli?", "is the CLI required?". Do NOT auto-invoke for general coding questions unrelated to Coding Friend itself.
| name | cf-commit |
| description | Smart conventional commit with diff analysis. Use when the user wants to commit changes — e.g. "commit this", "commit my changes", "save my work", "create a commit", "git commit", "commit what we did", "stage and commit". Also triggers when the user finishes a task and wants to commit the result. |
| created | 2026-02-17T00:00:00.000Z |
| updated | 2026-07-04T00:00:00.000Z |
CLI Requirement: NONE — Works without
coding-friend-cli. See CLI requirements for the full matrix.
Create a commit for the current changes. Hint: $ARGUMENTS
Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself):
bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-commit
If output is not empty, integrate returned sections: ## Before → before first step, ## Rules → apply throughout, ## After → after final step.
bash "${PLUGIN_ROOT}/skills/cf-commit/scripts/analyze-changes.sh"
Review the current conversation to understand what task was performed and which files were modified as part of that task.
git status shows files that were NOT part of the current task, do NOT include them.env, credentials, or secretsgit add . or git add -ASecret scan — after staging, check for accidental secrets:
bash "${PLUGIN_ROOT}/skills/cf-commit/scripts/scan-secrets.sh"
The script prints SECRETS=<count> and, if SECRETS > 0, shows matching lines with context.
If SECRETS > 0:
getApiKey() or TOKEN_TYPE are OK, actual secret values are NOTgit reset HEAD <file>), suggest adding to .gitignoreIf no $cf-review was run in the current conversation, show a soft suggestion:
No review found in this session — run
$cf-reviewfirst? (press Enter to skip and commit anyway)
If the user skips (presses Enter or says to proceed), continue. If they want a review, load $cf-review and resume $cf-commit after.
Follow conventional commits format:
<type>(<scope>): <subject>
<body - optional, concise bullet list>
Types: feat, fix, refactor, test, docs, chore, style, perf, ci
Rules:
- bullets, one line per bullet$ARGUMENTS is provided, use it as context for the messagegit commit -m "<message>"
Show the commit result to the user.