commit
根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交;不適用於需要 push 或建立 Pull Request 的情境。
- License 许可
- MIT
- 所属仓库
- cdcd72/skills
- 最近更新
- 2026-08-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- commit
- description
- 根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交;不適用於需要 push 或建立 Pull Request 的情境。
03 SKILL.md 正文
Commit
目的
根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交。
適用時機
- 需要根據目前 diff 建立單一提交
- 需要在
main分支上先切出功能分支再提交 - 需要避免空泛或不準確的提交訊息
流程
-
檢查目前分支與變更。
git branch --show-current git status -s git diff HEAD -
根據實際 diff 判斷分支類型、分支名稱與 commit message;若沒有實際變更,停止,不要建立空提交。
-
如果目前在
main分支,先建立新分支。git checkout -b <type>/<description> -
暫存並確認提交內容。
git add . git status -s git diff --cached -
建立單一提交。
git commit -m "<type>(<scope>): <description>"
規範
分支格式
<type>/<description>
type使用:feat,fix,docs,refactor,perf,test,build,ci,chore,styledescription使用英文、kebab-case、命令式描述- 不要加標點符號
提交訊息格式
<type>(<scope>): <description>
或省略 scope:
<type>: <description>
type同 branch typescope可選,使用受影響的模組或功能名稱description使用繁體中文- 必須根據實際 diff 撰寫
- 不要使用「更新檔案」、「修改內容」等空泛描述
- 不要加標點符號
- 重大變更使用
!或BREAKING CHANGE:
限制
- 只建立一個 commit
- 不要 push
- 不要 amend
- 不要提交 secrets、
.env、建置產物、暫存檔或無關檔案
04 同仓库更多 Skills
template-skill
Replace with description of the skill and when Agent should use it.
simple-sdd
simple sdd workflow for coding tasks. use when the user says 提案, 實作, or 歸檔 for a development request, or asks to follow a lightweight sdd process before coding. enforce proposal before implementation, wait for confirmation, complete one task at a time, report after each small step, and archive completed sdd work.
presentation-flow-writer
Guides the user through co-authoring a "簡報流程檔" (presentation flow document) — a structured input document written FOR a slide-generation AI agent, not a script or final slide copy — then turns it into a client-facing HTML review page. Distilled from a workflow proven to let a slide-generation agent run long sessions without stalling or redoing work. Use when the user wants to plan a talk/deck's narrative before generating slides, asks to design a "簡報流程" / "簡報大綱" / "投影片流程檔", wants a template for briefing a presentation-generation AI, or asks to turn an existing 簡報流程檔 into something a client can review and sign off on ("給客戶看的版本" / "簡報流程確認版" / HTML 確認頁).
merge-branch
Merge one local Git branch into another through a guarded workflow: inspect repository state, fetch remote references, analyze divergence, perform the local merge, resolve conflicts according to both branches' intent, run project validation, and report the result. Use when the user asks to merge source branch X into target branch Y, integrate one branch into another, or resolve conflicts caused by that local branch merge. Operate only with local Git commands. Never handle pull requests or merge requests. Never push unless the user gives a separate explicit instruction after reviewing the local result.
implementation-orchestrator
Turn engineering work into a reviewed execution baseline with a context pack, implementation plan, complexity routing, optional workstream breakdowns, execution briefs for coding agents or human executors, QA verification, and optional delivery updates. Use when the user wants to turn a bug, feature, refactor, review request, or technical task into an implementation plan, coordinate work across coding agents or human executors, or verify completed implementation against the approved plan.
gemma4-prompt-engineer
Based on the official Gemma 4 documentation and a curated practical knowledge base, assist in writing, optimizing, and diagnosing prompts tailored for the Google Gemma 4 model. When a user mentions Gemma 4 (including any of its sizes, such as E2B, E4B, 12B, 26B A4B, or 31B), needs to write/modify a Gemma 4 prompt, or asks about Gemma 4 control tokens, thinking mode, multimodal ordering, tool/function calling formats, or why an existing Gemma 4 prompt is underperforming, you must utilize this Skill rather than relying solely on general prompting knowledge.