docs(git): translate SKILL.md into English per guidelines
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
+25
-25
@@ -3,38 +3,38 @@ name: commit
|
||||
description: Group all pending file changes by conventional type and feature, then commit each group as {type}({scope}): {message}. Message style is full (What/Why/How/Who), brief (one line from git diff), or custom, chosen via decision tree. Use whenever changes must be committed; not for push or PR creation.
|
||||
---
|
||||
|
||||
# commit — 分組認可檔案變更
|
||||
# commit — group and commit file changes
|
||||
|
||||
## 步驟
|
||||
## Steps
|
||||
|
||||
1. 追蹤所有檔案變更:先 `git status --porcelain` 檢視全部變更,再逐組 `git add`(不可盲目 `git add -A` 後一次 commit)。
|
||||
2. 依「同類型 + 同需求/功能」將檔案變更分組,一組一個 commit。
|
||||
3. 每組依格式認可:`{類型}({需求 or 功能}): {訊息}`。
|
||||
1. Track every file change: inspect all changes with `git status --porcelain` first, then `git add` group by group. Never `git add -A` and commit everything at once.
|
||||
2. Group the changes by same type plus same requirement or feature. One group is one commit.
|
||||
3. Commit each group with the format `{type}({requirement or feature}): {message}`.
|
||||
|
||||
## 類型表
|
||||
## Type table
|
||||
|
||||
| 類型 | 用途 |
|
||||
| Type | Purpose |
|
||||
| --- | --- |
|
||||
| feat | 新增/修改功能 |
|
||||
| fix | 修補 bug |
|
||||
| docs | 文件 |
|
||||
| style | 格式(不影響程式碼運行的變動) |
|
||||
| refactor | 重構(既不是新增功能,也不是修補 bug 的程式碼變動) |
|
||||
| perf | 改善效能 |
|
||||
| test | 增加測試 |
|
||||
| chore | 建構程序或輔助工具的變動 |
|
||||
| revert | 撤銷先前的 commit |
|
||||
| feat | add or change a feature |
|
||||
| fix | fix a bug |
|
||||
| docs | documentation |
|
||||
| style | formatting; no change to how the code runs |
|
||||
| refactor | code change that neither adds a feature nor fixes a bug |
|
||||
| perf | improve performance |
|
||||
| test | add tests |
|
||||
| chore | build process or tooling change |
|
||||
| revert | revert an earlier commit |
|
||||
|
||||
## 訊息格式(三選一)
|
||||
## Message format (pick one of three)
|
||||
|
||||
依 `jsc-ask:ask` 規則詢問使用者;問詢紀錄或本 session 已有慣例就不再問。
|
||||
Ask the user per the `jsc-ask:ask` rules. Skip the question when the question record or this session already holds a convention.
|
||||
|
||||
1. **完整版**:包含做什麼(What)、為什麼做(Why)、怎麼做(How)、哪個功能做(Who)。
|
||||
2. **簡易版**:根據 `git diff` 總結出一句描述。
|
||||
3. **自訂**:使用者自行輸入訊息。
|
||||
1. **Full**: covers What, Why, How, and Who (which feature).
|
||||
2. **Brief**: one sentence summarized from `git diff`.
|
||||
3. **Custom**: the user types the message.
|
||||
|
||||
## 規則
|
||||
## Rules
|
||||
|
||||
1. 分組與訊息草擬的細節**必須以 sub agent 執行**,主 agent 只確認分組結果與執行 commit。
|
||||
2. 訊息一律 UTF-8 繁體中文(類型與 scope 除外)。
|
||||
3. 不可 push;push 與 PR 由 `jsc-git:pr` 負責。
|
||||
1. The grouping and message drafting details **MUST run as a sub agent**. The main agent only confirms the grouping and runs the commits.
|
||||
2. Write messages in UTF-8 Traditional Chinese (the type and scope stay in English), per the STE100 output rule.
|
||||
3. Never push. Push and PR belong to `jsc-git:pr`.
|
||||
|
||||
Reference in New Issue
Block a user