charted-continue
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseContext
上下文
- designDocPath: $ARGUMENTS[0]
- prNumber: $ARGUMENTS[1]
- designDocPath: $ARGUMENTS[0]
- prNumber: $ARGUMENTS[1]
Goal
目标
Read , inspect the state of PR #${prNumber}, and invoke exactly one downstream skill:
${designDocPath}| Condition | Skill to invoke |
|---|---|
| Scaffolding not done | |
| Next 🚧 test not implemented | |
| Next 🚧 test already implemented | |
读取 ,检查 PR #${prNumber} 的状态,并调用且仅调用一个下游 skill:
${designDocPath}| 条件 | 要调用的 Skill |
|---|---|
| 尚未完成脚手架搭建 | |
| 下一个 🚧 测试尚未实现 | |
| 下一个 🚧 测试已经实现 | |
Steps
步骤
1. Locate the PR section
1. 定位 PR 部分
In , find the section for PR #${prNumber} — a heading like or .
${designDocPath}# 🚧 PR#N - {title}# 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.
在 中,找到 PR #${prNumber} 对应的部分——标题格式类似 或 。
${designDocPath}# 🚧 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 scenario has a matching
### 🚧 {test_title}in a test file (test names are lower case).it.todo("{test_title}", ...) - WIP production files referenced in Tasks exist (classes/components tagged or equivalent stubs).
@deprecated 🚧 work in progress
Scaffolding is not done if any expected test file or WIP source file is missing, or if stubs with design-doc step comments do not yet exist.
it.todoIf scaffolding is not done → read and follow the skill with and . Stop.
charted-scaffold${designDocPath}${prNumber}当 PR #${prNumber} 满足以下所有条件时,脚手架搭建即视为 已完成:
- PR 的 Testing Strategy 场景对应的测试文件均已存在。
- 每个 场景都在测试文件中有一个匹配的
### 🚧 {test_title}(测试名称为小写)。it.todo("{test_title}", ...) - Tasks 中引用的 WIP 生产文件均已存在,例如带有 标签的类、组件或等效的存根。
@deprecated 🚧 work in progress
如果缺少任何预期的测试文件或 WIP 源文件,或者带有设计文档步骤注释的 存根尚不存在,则脚手架搭建 尚未完成。
it.todo如果脚手架搭建尚未完成 → 读取并遵循 skill,并传入 和 。停止。
charted-scaffold${designDocPath}${prNumber}3. Find the next pending test
3. 查找下一个待处理测试
In the PR's Testing Strategy, pick the first heading still marked (not ).
### 🚧 {test_title}### ✅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 whose name matches the pending test title (case-insensitive). Prefer the file under the component or unit named in the nearest heading above the scenario.
it.todo## {Component}Record the path as .
testFilePath在项目中搜索名称与待处理测试标题匹配的 (不区分大小写)。优先选择位于该场景上方最近的 标题所指定的组件或单元下的文件。
it.todo## {Component}将路径记录为 。
testFilePath5. Classify the test
5. 判断测试状态
Open and inspect the body for the pending test:
testFilePathit.todo- Not implemented — body is empty or contains only step-by-step comments copied from the design doc (no ,
expect, mount helpers, or other executable test code).inject - Implemented — body contains actual test code beyond comments.
打开 ,检查待处理测试对应的 内容:
testFilePathit.todo- 尚未实现——内容为空,或仅包含从设计文档复制的分步注释,不含 、
expect、mount helpers 或其他可执行测试代码。inject - 已经实现——内容包含注释之外的实际测试代码。
6. Invoke the downstream skill
6. 调用下游 skill
Not implemented → read and follow the skill with and .
charted-red${designDocPath}${testFilePath}Implemented → read and follow the skill with and .
charted-green${designDocPath}${testFilePath}尚未实现 → 读取并遵循 skill,并传入 和 。
charted-red${designDocPath}${testFilePath}已经实现 → 读取并遵循 skill,并传入 和 。
charted-green${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 的使用方式和设计文档复选框更新。