charted-continue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Context

上下文

  • designDocPath: $ARGUMENTS[0]
  • prNumber: $ARGUMENTS[1]
  • designDocPath: $ARGUMENTS[0]
  • prNumber: $ARGUMENTS[1]

Goal

目标

Read
${designDocPath}
, inspect the state of PR #${prNumber}, and invoke exactly one downstream skill:
ConditionSkill to invoke
Scaffolding not done
charted-scaffold
Next 🚧 test not implemented
charted-red
Next 🚧 test already implemented
charted-green
读取
${designDocPath}
,检查 PR #${prNumber} 的状态,并调用且仅调用一个下游 skill:
条件要调用的 Skill
尚未完成脚手架搭建
charted-scaffold
下一个 🚧 测试尚未实现
charted-red
下一个 🚧 测试已经实现
charted-green

Steps

步骤

1. Locate the PR section

1. 定位 PR 部分

In
${designDocPath}
, find the section for PR #${prNumber} — a heading like
# 🚧 PR#N - {title}
or
# PR#N - {title}
.
Read its Tasks and Testing Strategy subsections. The design doc is the single source of truth for what belongs to this PR.
在
${designDocPath}
中,找到 PR #${prNumber} 对应的部分——标题格式类似
# 🚧 PR#N - {title}
或
# PR#N - {title}
。
阅读其 Tasks 和 Testing Strategy 子部分。设计文档是确定该 PR 应包含内容的唯一事实来源。

2. Check scaffolding

2. 检查脚手架搭建情况

Scaffolding is done when all of the following hold for PR #${prNumber}:
  • Test file(s) exist for the PR's Testing Strategy scenarios.
  • Each
    ### 🚧 {test_title}
    scenario has a matching
    it.todo("{test_title}", ...)
    in a test file (test names are lower case).
  • WIP production files referenced in Tasks exist (classes/components tagged
    @deprecated 🚧 work in progress
    or equivalent stubs).
Scaffolding is not done if any expected test file or WIP source file is missing, or if
it.todo
stubs with design-doc step comments do not yet exist.
If scaffolding is not done → read and follow the
charted-scaffold
skill with
${designDocPath}
and
${prNumber}
. Stop.
当 PR #${prNumber} 满足以下所有条件时,脚手架搭建即视为 已完成:
  • PR 的 Testing Strategy 场景对应的测试文件均已存在。
  • 每个
    ### 🚧 {test_title}
    场景都在测试文件中有一个匹配的
    it.todo("{test_title}", ...)
    (测试名称为小写)。
  • Tasks 中引用的 WIP 生产文件均已存在,例如带有
    @deprecated 🚧 work in progress
    标签的类、组件或等效的存根。
如果缺少任何预期的测试文件或 WIP 源文件,或者带有设计文档步骤注释的
it.todo
存根尚不存在,则脚手架搭建 尚未完成。
如果脚手架搭建尚未完成 → 读取并遵循
charted-scaffold
skill,并传入
${designDocPath}
和
${prNumber}
。停止。

3. Find the next pending test

3. 查找下一个待处理测试

In the PR's Testing Strategy, pick the first heading still marked
### 🚧 {test_title}
(not
### ✅
).
If every test is
### ✅
, report that PR #${prNumber} is complete and stop.
在该 PR 的 Testing Strategy 中,选择第一个仍标记为
### 🚧 {test_title}
(而非
### ✅
)的标题。
如果所有测试均为
### ✅
,则报告 PR #${prNumber} 已完成,并 停止。

4. Locate the matching test file

4. 定位匹配的测试文件

Search the project for the
it.todo
whose name matches the pending test title (case-insensitive). Prefer the file under the component or unit named in the nearest
## {Component}
heading above the scenario.
Record the path as
testFilePath
.
在项目中搜索名称与待处理测试标题匹配的
it.todo
(不区分大小写)。优先选择位于该场景上方最近的
## {Component}
标题所指定的组件或单元下的文件。
将路径记录为
testFilePath
。

5. Classify the test

5. 判断测试状态

Open
testFilePath
and inspect the
it.todo
body for the pending test:
  • Not implemented — body is empty or contains only step-by-step comments copied from the design doc (no
    expect
    ,
    inject
    , mount helpers, or other executable test code).
  • Implemented — body contains actual test code beyond comments.
打开
testFilePath
,检查待处理测试对应的
it.todo
内容:
  • 尚未实现——内容为空,或仅包含从设计文档复制的分步注释,不含
    expect
    、
    inject
    、mount helpers 或其他可执行测试代码。
  • 已经实现——内容包含注释之外的实际测试代码。

6. Invoke the downstream skill

6. 调用下游 skill

Not implemented → read and follow the
charted-red
skill with
${designDocPath}
and
${testFilePath}
.
Implemented → read and follow the
charted-green
skill with
${designDocPath}
and
${testFilePath}
.
尚未实现 → 读取并遵循
charted-red
skill,并传入
${designDocPath}
和
${testFilePath}
。
已经实现 → 读取并遵循
charted-green
skill,并传入
${designDocPath}
和
${testFilePath}
。

Rules

规则

  • Invoke one downstream skill per run — never scaffold, red, and green in the same turn.
  • Do not skip ahead to a later 🚧 test while an earlier one is still pending.
  • Do not implement production code or enable tests directly — delegate to the downstream skill.
  • When reading downstream skills, follow their instructions fully, including Wallaby usage and design-doc checkbox updates.
  • 每次运行仅调用 一个 下游 skill——绝不能在同一轮中依次调用 scaffold、red 和 green。
  • 当前面的测试仍处于待处理状态时,不得跳过后续 🚧 测试。
  • 不要直接实现生产代码或启用测试——将任务委派给下游 skill。
  • 读取下游 skill 时,应完整遵循其说明,包括 Wallaby 的使用方式和设计文档复选框更新。