fast

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/fast - Zero-Ceremony Execution

/fast - 无繁琐流程执行

Operator Context

操作者背景

This skill implements the Fast tier from the five-tier task hierarchy (Fast > Quick > Simple > Medium > Complex). It exists because the full ceremony of plan files, agent routing, and quality gates is wasteful for a typo fix. The process should scale down to match the task.

该技能实现了五级任务层级中的Fast层级（Fast > Quick > Simple > Medium > Complex）。它的存在是因为对于拼写错误修复这类任务来说，完整的规划文件、Agent路由和质量校验流程过于冗余。流程应根据任务规模灵活调整。

Hardcoded Behaviors (Always Apply)

硬编码行为（始终适用）

3-Edit Scope Limit: If the task requires more than 3 file edits, STOP and redirect to
```
/quick
```
. The work done so far is preserved — do not restart. This gate exists because uncapped "fast" tasks silently grow into untracked large changes.
No Plan File: Do not create
```
task_plan.md
```
. The overhead of planning exceeds the task itself at this tier.
No Subagent Spawning: Execute inline. Subagents add latency and context setup cost that dwarfs the actual work.
No Research Phase: If the task requires reading documentation, investigating behavior, or understanding unfamiliar code, it is not a Fast task. Redirect to
```
/quick --research
```
.
No New Dependencies: If the task requires adding imports from new packages, installing libraries, or modifying dependency files (go.mod, package.json, requirements.txt), redirect to
```
/quick
```
.
CLAUDE.md Compliance: Read and follow repository CLAUDE.md before execution.
Branch Safety: Create a feature branch if currently on main/master. Even fast tasks get proper branches.
Commit After Edit: Every fast task ends with a commit. Uncommitted fast edits defeat the auditability that justifies using the system at all.

最多3次编辑的范围限制：如果任务需要超过3次文件编辑，立即停止并转至/quick处理。已完成的工作将被保留——请勿重启任务。设置该限制是为了防止无约束的「快速」任务悄无声息地演变为无跟踪的大型变更。
不生成规划文件：请勿创建
```
task_plan.md
```
。在该层级，规划的开销远大于任务本身的工作量。
不生成子Agent：直接内联执行。子Agent会增加延迟和上下文设置成本，这些成本远超实际任务的工作量。
无调研阶段：如果任务需要阅读文档、调研行为逻辑或理解不熟悉的代码，则不属于Fast任务。请转至
```
/quick --research
```
处理。
不新增依赖：如果任务需要从新包导入内容、安装库或修改依赖文件（go.mod、package.json、requirements.txt等），请转至/quick处理。
遵循CLAUDE.md：执行前请阅读并遵循仓库中的CLAUDE.md。
分支安全：如果当前处于main/master分支，请创建功能分支。即使是快速任务也应使用规范分支。
编辑后立即提交：每个快速任务都必须以提交结尾。未提交的快速编辑会破坏使用该系统的核心价值——可审计性。

Default Behaviors (ON unless disabled)

默认行为（默认开启，可关闭）

STATE.md Logging: Append completed task to STATE.md quick tasks table (create if absent)
Conventional Commits: Use conventional commit format for the commit message
Edit Counting: Track edits during execution to enforce the 3-edit scope gate

STATE.md日志记录：将已完成的任务追加至STATE.md的快速任务表格中（若文件不存在则创建）
使用conventional commit格式：提交信息采用conventional commit格式
编辑次数统计：执行过程中跟踪编辑次数，以强制执行最多3次编辑的范围限制

Optional Behaviors (OFF unless enabled)

可选行为（默认关闭，可开启）

No Commit Mode (
```
--no-commit
```
): Skip the commit step (for when the user wants to batch changes)
Dry Run (
```
--dry-run
```
): Show what would change without editing

无提交模式（
```
--no-commit
```
）：跳过提交步骤（适用于用户需要批量变更的场景）
试运行模式（
```
--dry-run
```
）：展示将要进行的变更，但不实际编辑文件

What This Skill CAN Do

该技能可完成的任务

Fix typos, rename variables, update config values, fix imports
Make 1-3 targeted file edits and commit them
Log the action to STATE.md for auditability

修复拼写错误、重命名变量、更新配置值、修复导入语句
完成1-3次针对性文件编辑并提交
将操作记录至STATE.md以保证可审计性

What This Skill CANNOT Do

该技能不可完成的任务

Research unfamiliar code or APIs (redirect to
```
/quick --research
```
)
Add new dependencies (redirect to
```
/quick
```
)
Edit more than 3 files (redirect to
```
/quick
```
)
Run quality gates or parallel reviews (those belong to Simple+ tiers)
Create plans or spawn subagents

调研不熟悉的代码或API（请转至
```
/quick --research
```
）
新增依赖（请转至/quick）
编辑超过3个文件（请转至/quick）
执行质量校验或并行评审（这些属于Simple及以上层级的任务）
创建规划或生成子Agent

Instructions

操作步骤

Phase 1: UNDERSTAND

阶段1：理解任务

Goal: Confirm the task is Fast-eligible and know exactly what to change.

Step 1: Read the request

Parse the user's request to identify:

Which file(s) need editing
What specific change is needed
Whether this is clearly a 1-3 edit task

Step 2: Scope check

Ask these questions silently (do not display to user):

Does this need research or investigation? If yes -> redirect to
```
/quick --research
```
Does this touch more than 3 files? If yes -> redirect to
```
/quick
```
Does this add new dependencies? If yes -> redirect to
```
/quick
```
Is the change ambiguous or underspecified? If yes -> ask user for clarification

If redirecting, say:

This task exceeds /fast scope ([reason]). Redirecting to /quick.

Then invoke the quick skill with the original request.

Step 3: Locate target files

Read the file(s) that need editing. Confirm the exact lines to change.

GATE: Task is confirmed Fast-eligible (1-3 edits, no research, no new deps). Target files identified and read.

目标：确认任务符合Fast层级要求，并明确具体修改内容。

步骤1：读取用户请求

解析用户请求，确定：

需要编辑哪些文件
具体需要进行哪些修改
该任务是否明确属于1-3次编辑的范畴

步骤2：范围检查

静默自问以下问题（无需展示给用户）：

是否需要调研或调查？若是 -> 转至
```
/quick --research
```
是否涉及超过3个文件？若是 -> 转至/quick
是否需要新增依赖？若是 -> 转至/quick
变更需求是否模糊或不明确？若是 -> 向用户请求澄清

若需要转至其他流程，请告知：

该任务超出/fast的处理范围（[原因]）。将转至/quick处理。

随后调用quick技能处理原请求。

步骤3：定位目标文件

读取需要编辑的文件，确认具体需要修改的行。

准入条件：任务已确认符合Fast层级要求（1-3次编辑、无需调研、无需新增依赖），目标文件已定位并读取。

Phase 2: DO

阶段2：执行修改

Goal: Make the edits.

Step 1: Execute edits

Make the changes using Edit tool. Track the number of files edited.

Step 2: Mid-execution scope check

After each edit, check: have we hit 3 edits? If the task needs MORE edits to complete:

Scope exceeded during execution (3+ edits needed). Preserving work done.
Redirecting remainder to /quick.

Hand off to

/quick

with context about what was already done.

GATE: All edits complete. Edit count is 1-3.

目标：完成文件编辑。

步骤1：执行编辑

使用编辑工具完成修改，跟踪已编辑的文件数量。

步骤2：执行过程中的范围检查

每次编辑后检查：是否已达到3次编辑？若任务需要更多编辑才能完成：

执行过程中超出范围（需要3次以上编辑）。已完成的工作将被保留。
剩余任务将转至/quick处理。

将任务转至/quick，并告知已完成的编辑内容。

准入条件：所有编辑已完成，编辑次数为1-3次。

Phase 3: COMMIT

阶段3：提交变更

Goal: Commit the changes with a clean message.

Step 1: Check branch

If on main/master, create a feature branch first:

bash

git checkout -b fast/<brief-description>

Step 2: Stage and commit

bash

git add <specific-files>
git commit -m "$(cat <<'EOF'
<type>: <description>
EOF
)"

Use conventional commit format. The type is usually

fix:

chore:

, or

refactor:

for fast tasks.

GATE: Commit succeeded. Verify with

git log -1 --oneline

目标：使用规范的提交信息完成变更提交。

步骤1：检查分支

若当前处于main/master分支，请先创建功能分支：

bash

git checkout -b fast/<简要描述>

步骤2：暂存并提交

bash

git add <具体文件>
git commit -m "$(cat <<'EOF'
<类型>: <描述>
EOF
)"

使用conventional commit格式。Fast任务的提交类型通常为

fix:

、

chore:

或

refactor:

。

准入条件：提交成功。可通过

git log -1 --oneline

验证。

Phase 4: LOG

阶段4：记录日志

Goal: Record the task for auditability.

Step 1: Append to STATE.md

If STATE.md exists in the repo root, append to the quick tasks table. If it does not exist, create it.

Format:

markdown

undefined

目标：记录任务以保证可审计性。

步骤1：追加至STATE.md

若仓库根目录存在STATE.md，则将任务追加至快速任务表格中。若文件不存在，则创建该文件。

格式：

markdown

undefined

Quick Tasks

快速任务

Date	ID	Description	Commit	Tier
YYYY-MM-DD	-	<description>	<short-hash>	fast


Fast tasks do not get task IDs (that is a Quick-tier feature). Use `-` for the ID column.

**Step 2: Display summary**

=================================================================== FAST: <description>

Files edited: <N> Commit: <hash> on <branch> Logged: STATE.md

===================================================================

---

日期	ID	描述	提交	层级
YYYY-MM-DD	-	<描述>	<短哈希值>	fast


Fast任务无需分配任务ID（这是Quick层级的特性）。ID列使用`-`填充。

**步骤2：展示总结信息**

=================================================================== FAST: <描述>

已编辑文件数：<N> 提交信息：<哈希值> on <分支> 日志记录：已写入STATE.md

===================================================================

---

Error Handling

错误处理

Error: Scope Exceeded Mid-Execution

错误：执行过程中超出范围

Cause: Task turned out to need more than 3 edits Solution: Stop, preserve work, redirect to

/quick

with context about completed edits. Do not undo work already done.

原因：任务实际需要超过3次编辑 解决方案：停止执行，保留已完成的工作，将剩余任务转至/quick处理。请勿撤销已完成的修改。

Error: Ambiguous Request

错误：请求模糊

Cause: Cannot determine exact files or changes from the request Solution: Ask user one clarifying question. If still ambiguous after one round, redirect to

/quick --discuss

原因：无法从请求中确定具体需要编辑的文件或修改内容 解决方案：向用户提出一个澄清问题。若一次澄清后仍不明确，请转至

/quick --discuss

。

Error: On Main Branch

错误：处于主分支

Cause: Currently on main/master Solution: Create

fast/<description>

branch before editing. Never commit directly to main.

原因：当前处于main/master分支 解决方案：编辑前创建

fast/<描述>

分支。禁止直接向主分支提交。

Anti-Patterns

反模式

Anti-Pattern 1: Using Fast for Investigation

反模式1：使用Fast层级进行调研

What it looks like: Reading 5 files to understand a bug before fixing it Why wrong: Investigation is research. Fast is for when you already know what to change. Do instead: Use

/quick --research

for tasks that need understanding first.

表现：修复bug前先读取5个文件以理解问题 错误原因：调研属于研究范畴。Fast层级仅适用于已明确修改内容的任务。 正确做法：对于需要先理解的任务，使用

/quick --research

。

Anti-Pattern 2: Skipping the Commit

反模式2：跳过提交步骤

What it looks like: Making fast edits but not committing because "it's just a small change" Why wrong: Uncommitted changes are invisible to the audit trail. The whole point of /fast over raw editing is traceability. Do instead: Always commit. Use

--no-commit

only when explicitly batching.

表现：完成快速编辑但不提交，理由是「只是个小修改」 错误原因：未提交的变更在审计追踪中不可见。/fast相较于直接编辑的核心价值就是可追溯性。 正确做法：始终提交变更。仅在明确需要批量处理时使用

--no-commit

参数。

Anti-Pattern 3: Stretching Scope

反模式3：扩大任务范围

What it looks like: "While I'm here, let me also fix this other thing" — turning 2 edits into 6 Why wrong: Scope creep in fast mode produces untracked large changes with no plan or review Do instead: Stop at 3 edits. Open a new

/fast

/quick

for additional work.

表现：「既然我在这里，顺便把这个也修了」——将2次编辑变成6次 错误原因：快速模式下的范围蔓延会产生无规划、无评审的无跟踪大型变更 正确做法：最多完成3次编辑。额外的工作请新建

/fast

或

/quick

任务。

Anti-Rationalization

反合理化

Rationalization	Why It's Wrong	Required Action
"Just one more edit won't hurt"	The 3-edit gate exists to prevent silent scope creep	Redirect to /quick at edit 4
"This is basically fast, just needs a little research"	Research means uncertainty; uncertainty means /quick	Redirect to /quick --research
"No need to commit a one-line change"	One-line changes cause one-line bugs that are invisible without commits	Commit every fast task
"STATE.md logging is overhead"	Without logging, fast tasks are invisible — defeating auditability	Always log to STATE.md

合理化借口	错误原因	要求操作
"再多加一次编辑也没关系"	3次编辑的限制是为了防止悄无声息的范围蔓延	第4次编辑时转至/quick
"这个任务基本符合Fast要求，只是需要一点调研"	调研意味着不确定性；有不确定性的任务应使用/quick	转至 `/quick --research`
"单行修改没必要提交"	单行修改可能引发单行bug，没有提交记录的话这些bug难以追踪	每个Fast任务都必须提交
"STATE.md日志记录是额外开销"	没有日志记录的话，Fast任务将不可见——这会破坏可审计性	始终将任务记录至STATE.md