vibe-continue

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/vibe-continue - Resume Current Flow

/vibe-continue

的目标是恢复当前目录承载的

flow

所对应任务的上下文，但恢复顺序必须是“共享事实优先，本地 handoff 补充”，而不是反过来。

核心原则：

先读共享真源，再读
```
.agent/context/task.md
```
。
```
.agent/context/task.md
```
是 handoff，不是共享真源。
handoff 的维护义务以
```
docs/standards/handoff-governance-standard.md
```
为准；发现与现场不一致时必须修正。
不在 continue 阶段发明不存在的 Shell 修复动作。

Announce at start: "我正在使用 /vibe-continue 技能来恢复当前 flow 的任务上下文。"

The goal of

/vibe-continue

is to restore the context of the task corresponding to the

flow

hosted in the current directory, but the restoration order must be "shared facts first, local handoff as supplement", not the other way around.

Core Principles:

Read the shared source of truth first, then read
```
.agent/context/task.md
```
.
```
.agent/context/task.md
```
is a handoff, not a shared source of truth.
The maintenance obligation of handoff shall follow
```
docs/standards/handoff-governance-standard.md
```
; if inconsistencies with the current scene are found, corrections must be made.
Do not invent non-existent Shell repair actions during the continue phase.

Announce at start: "I am using the /vibe-continue skill to restore the task context of the current flow."

Truth Sources

以下语义以标准为准：

```
docs/standards/skill-standard.md
```
```
docs/standards/command-standard.md
```

docs/standards/shell-capability-design.md

```
docs/standards/git-workflow-standard.md
```

docs/standards/handoff-governance-standard.md

```
docs/standards/glossary.md
```

特别约束：

flow

不等于

worktree

、

branch

或

workflow

。见

docs/standards/glossary.md

。

.agent/context/task.md

的读取、写入与修正义务以

docs/standards/handoff-governance-standard.md

为准。

The following semantics shall be based on the standards:

```
docs/standards/skill-standard.md
```
```
docs/standards/command-standard.md
```

docs/standards/shell-capability-design.md

```
docs/standards/git-workflow-standard.md
```

docs/standards/handoff-governance-standard.md

```
docs/standards/glossary.md
```

Special Constraints:

flow

is not equivalent to

worktree

branch

, or

workflow

. Refer to

docs/standards/glossary.md

The obligations for reading, writing, and correcting

.agent/context/task.md

shall follow

docs/standards/handoff-governance-standard.md

Command Boundary

```
/vibe-continue
```
负责解释当前现场并给出继续建议。
Shell 命令只用于读取共享真源和当前现场的确定性事实。
```
git
```
/
```
gh
```
可用于补充 branch、dirty、PR 等现场事实。
如果需要某个环境修正动作，必须使用仓库中真实存在且已文档化的入口；不要发明未验证的修复命令。

```
/vibe-continue
```
is responsible for interpreting the current scene and providing suggestions for continuation.
Shell commands are only used to read the shared source of truth and deterministic facts of the current scene.
```
git
```
/
```
gh
```
can be used to supplement on-site facts such as branch, dirty status, PR, etc.
If an environment correction action is required, you must use a real, documented entry in the repository; do not invent unvalidated repair commands.

Restore Order

/vibe-continue

默认按以下顺序恢复：

当前

git

现场（

git branch --show-current

、

git status --short

、必要时

gh pr view

）

$(git rev-parse --git-common-dir)/vibe/registry.json

$(git rev-parse --git-common-dir)/vibe/tasks/<task-id>/task.json

$(git rev-parse --git-common-dir)/vibe/worktrees.json

（如果存在，只作兼容期辅助线索）

```
.agent/context/task.md
```
（如果存在）

必要时再补充：

当前 branch
```
git status --short
```
当前 PR / review 事实

/vibe-continue

restores in the following order by default:

Current

git

scene (

git branch --show-current

git status --short

gh pr view

if necessary)

$(git rev-parse --git-common-dir)/vibe/registry.json

$(git rev-parse --git-common-dir)/vibe/tasks/<task-id>/task.json

```
$(git rev-parse --git-common-dir)/vibe/worktrees.json
```
(if exists, only as a compatibility period auxiliary clue)
```
.agent/context/task.md
```
(if exists)

Supplement with the following if necessary:

Current branch
```
git status --short
```
Current PR / review facts

Workflow

Step 1: 识别当前目录承载的 flow 对应 task

Step 1: Identify the task corresponding to the flow hosted in the current directory

优先从

git

现场、共享

registry.json

与 task detail 识别：

当前 task
```
next_step
```
```
plan_path
```
当前 runtime 绑定事实
```
primary_issue_ref
```
（若存在，它就是
```
task issue
```
的显式落点）

worktrees.json

若存在，只能作为兼容期 hint，不能先于

registry.json

抢占当前 task 识别权。

如果共享真源中无法识别当前 task，不要把

task.md

直接抬升成替代真源；它只能作为本地 handoff 线索。

Prioritize identification from the

git

scene, shared

registry.json

, and task details:

Current task
```
next_step
```
```
plan_path
```
Current runtime binding facts
```
primary_issue_ref
```
(if exists, it is the explicit landing point of the
```
task issue
```
)

worktrees.json

exists, it can only be used as a compatibility period hint, and cannot preempt the current task identification right before

registry.json

If the current task cannot be identified from the shared source of truth, do not directly elevate

task.md

as an alternative source of truth; it can only be used as a local handoff clue.

Step 2: 读取本地 handoff

Step 2: Read local handoff

如果

.agent/context/task.md

存在，则把它作为以下信息的补充来源：

本轮已完成
当前判断
blockers
关键文件

若其内容与当前真源或现场不一致，必须在退出前修正 handoff，不能直接沿用旧判断。

如果它缺失，不阻断 continue；只说明当前缺少本地 handoff。

.agent/context/task.md

exists, use it as a supplementary source for the following information:

Completed items in this round
Current judgments
Blockers
Key files

If its content is inconsistent with the current source of truth or scene, you must correct the handoff before exiting, and cannot directly use the old judgment.

If it is missing, it does not block the continue process; it only indicates that there is no local handoff currently.

Step 3: 交叉核对当前现场

Step 3: Cross-check the current scene

用确定性事实补全当前视图，例如：

当前 branch
dirty / clean
当前 PR 状态

continue 阶段可以报告不一致，但不要把查询命令说成“自动对齐”，也不要调用未验证的隐式修复动作。

Complete the current view with deterministic facts, such as:

Current branch
dirty / clean status
Current PR status

During the continue phase, you can report inconsistencies, but do not refer to query commands as "auto-alignment", and do not call unvalidated implicit repair actions.

Step 4: 给出继续建议

Step 4: Provide continuation suggestions

建议优先级如下：

如果
```
plan_path
```
存在，优先建议按计划继续。
如果只有
```
next_step
```
，则建议按当前 task 的下一步继续。
如果只有本地
```
task.md
```
handoff，则把它明确标注为本地补充线索，而不是共享事实。

The priority of suggestions is as follows:

If
```
plan_path
```
exists, prioritize suggesting to continue according to the plan.
If only
```
next_step
```
exists, suggest continuing with the next step of the current task.
If only the local
```
task.md
```
handoff exists, clearly mark it as a local supplementary clue, not a shared fact.

Suggested Output

📋 Session Resume

📁 Current Scene
  • worktree: <worktree>
  • branch: <branch>
  • state: dirty|clean

📌 Current Task
  • task: <task-id>
  • next step: <next-step>
  • plan: <plan-path|none>

📝 Local Handoff
  • task.md: present|missing
  • blockers: <summary>

💡 Suggested Action
  • continue with <plan-path|next-step>

📋 Session Resume

📁 Current Scene
  • worktree: <worktree>
  • branch: <branch>
  • state: dirty|clean

📌 Current Task
  • task: <task-id>
  • next step: <next-step>
  • plan: <plan-path|none>

📝 Local Handoff
  • task.md: present|missing
  • blockers: <summary>

💡 Suggested Action
  • continue with <plan-path|next-step>

Design Decisions

continue 先恢复共享事实，再读取本地 handoff。
```
task.md
```
的作用是补充解释，不是代替真源。
continue 报告现场差异，但不发明未验证的自动修复动作。

The continue process restores shared facts first, then reads the local handoff.
The role of
```
task.md
```
is to provide supplementary explanations, not to replace the source of truth.
The continue phase reports scene differences, but does not invent unvalidated automatic repair actions.