full-send

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Full Send

Full Send

The user invoked this because they are not watching this thread and want the work done end-to-end. Your updates and your final message go unread until long after you stop. You own the work from its current state to a merged PR.
The user grants you permission to:
  • Merge the PR once the merge gate passes.
  • Force-push the PR's own branch with
    --force-with-lease
    after a rebase.
  • Use the test methods that Proof needs, without asking first.
用户调用此 skill,是因为他们当前没有关注本线程,并希望将工作端到端完成。你的更新和最终消息会直到你停止工作很久之后才会被查看。你需要负责从当前状态到 PR 合并的全过程。
用户授予你以下权限:
  • merge gate 通过后合并该 PR。
  • rebase 后,使用
    --force-with-lease
    force-push 该 PR 自己的分支。
  • 按 Proof 所需使用测试方法,无需事先询问。

Testing permission

测试权限

Invoking this skill is the permission. If a project file or other instruction says to ask before a test method, or to leave testing to the user, this request replaces that rule for this task.
That includes ask-first rules for computer use, browser automation, simulators and devices, running the app or a dev server, screenshots, and visual checks. Use the method that gives direct proof. List it in the report.
Rules about how to test still apply. Follow rules that name the correct command, fixture, or check. This permission only removes the ask-first or leave-it-to-the-user step. If a preferred method cannot prove the change, use a gated method under this permission.
It covers only the tests needed for this task. It does not add permission for the steps under "Asking the user", such as production changes or data deletion. It also does not bypass a harness or system approval prompt if one appears.
调用此 skill 即表示已获得许可。如果项目文件或其他指令要求在某种测试方法前询问,或将测试留给用户,本请求会在本任务中取代该规则。
这也包括针对 computer use、browser automation、simulator 和 device、运行 app 或 dev server、screenshot 以及 visual check 的先询问规则。使用能够提供直接 Proof 的方法,并在报告中列出。
关于如何测试的规则仍然适用。遵循指明正确 command、fixture 或 check 的规则。本许可仅取消先询问或留给用户处理的步骤。如果首选方法无法证明变更,则在本许可范围内使用受控(gated)方法。
它仅涵盖本任务所需的测试,不会授予“询问用户”部分所列步骤的权限,例如 production 变更或数据删除。如果出现 harness 或系统 approval prompt,也不会绕过它。

Steps

步骤

  1. Finish the change. Complete the goal from the user's request with the smallest change that works. Fix the case that happened, not every case that could. If you are on the default branch, create a branch first.
  2. Prove it. Get proof for every change you made. See "Proof".
  3. Get feedback. Use the
    sol-loop
    skill to verify changes. Re-prove any behavior a fix touches.
  4. File the PR with the
    file-pr
    skill. Rebase onto the latest default branch first. Add one short line to the description that says how you proved the change.
  5. Babysit the PR with the
    babysit-pr
    skill. Fix CI failures and real human review findings. Get proof for each fix before you push it.
  6. Merge when the merge gate passes.
  7. Report in your final message: the PR link, the merge commit, your proof, and each decision you made for the user.
Stay active from step 1 to step 7. If you end your turn while checks are pending, the work stops, because nobody will prompt you again. Wait with the watcher from
babysit-pr
, so something wakes you when the PR changes. In T3 Code that is
watch_pull_request
. If you stop before the merge, call
unwatch_pull_request
first.
  1. 完成变更。 根据用户请求完成目标,并采用能够奏效的最小改动。修复实际发生的情况,而不是所有可能发生的情况。如果当前位于 default branch,请先创建 branch。
  2. 证明变更。 为每项改动取得 Proof。参见“Proof”。
  3. 获取反馈。 使用
    sol-loop
    skill 验证变更。重新证明修复所影响的任何行为。
  4. 提交 PR。 使用
    file-pr
    skill。先 rebase 到最新的 default branch。向 description 添加一行简短说明,写明你如何证明该变更。
  5. 看护 PR。 使用
    babysit-pr
    skill。修复 CI 失败和人工审查意见。每次 push 修复前先取得 Proof。
  6. 合并。 merge gate 通过后执行 merge。
  7. 报告。 在最终消息中报告:PR 链接、merge commit、Proof,以及你替用户作出的每项决定。
从步骤 1 持续执行到步骤 7。如果在检查仍待处理时结束当前轮次,工作就会停止,因为不会有人再次提醒你。使用
babysit-pr
中的 watcher 等待,这样 PR 发生变化时会有机制唤醒你。在 T3 Code 中,该 watcher 是
watch_pull_request
。如果在 merge 前停止,请先调用
unwatch_pull_request
。

Proof

Proof

Proof is evidence you observed yourself in this session: command output, a reproduction, a screenshot. Use the most direct proof the change allows:
  • Reproduce the original failure, apply the fix, then watch the same reproduction pass.
  • Run the checks that the repo's CI runs (typecheck, lint, tests).
  • Add one focused test that fails without the fix, when the behavior has none and the repo has a test setup.
  • For UI and runtime behavior, run the app and look at the change. Green mocked tests do not prove that the user experience works. Attach screenshots to the PR when they help and you have a way to upload them.
When you cannot find a way to prove a change, you do not have full confidence. Ask the user.
Proof 是你在本次会话中亲自观察到的证据,例如命令输出、问题复现或截图。选择该变更所允许的最直接 Proof:
  • 复现原有 failure,应用修复,然后确认同一复现步骤能够通过。
  • 运行 repo 的 CI 所执行的 checks(typecheck、lint、tests)。
  • 如果该行为尚无测试且 repo 具备 test setup,请添加一个聚焦的 test,确保没有修复时该测试会失败。
  • 对于 UI 和 runtime behavior,运行 app 并查看变更。绿色的 mocked tests 不能证明用户体验正常。在有帮助且具备上传方式时,将 screenshots 附到 PR。
如果找不到证明变更的方法,就无法拥有充分信心。此时询问用户。

Merge gate

Merge gate

Full confidence means all of these are true on the latest commit:
  • Your proof covers every change in the diff.
  • Required checks are green.
  • Every review comment is fixed or answered with a written reason, and no review thread is unresolved.
  • No human review still requests changes.
  • The branch is up to date with the default branch, and GitHub reports it as mergeable.
Merge with the method the repo uses. Check the allowed methods and recent merged PRs. If the repo uses a merge queue or auto-merge, stay until GitHub reports the PR as merged. Merge through branch protection as configured. Never use
--admin
or other bypasses.
对于最新 commit,只有以下条件全部成立,才算具备充分信心:
  • Proof 覆盖 diff 中的每项变更。
  • 必需的 checks 全部为绿色状态。
  • 每条 review comment 均已修复,或已书面说明理由,且没有未解决的 review thread。
  • 没有任何人工 review 仍在要求修改。
  • branch 已与 default branch 保持同步,并且 GitHub 报告其可以 merge。
使用 repo 采用的 merge 方式。检查允许的合并方式和近期已合并的 PR。如果 repo 使用 merge queue 或 auto-merge,请持续等待,直到 GitHub 报告该 PR 已合并。按照配置通过 branch protection 执行 merge。绝不使用
--admin
或其他绕过方式。

Asking the user

询问用户

A question in a normal message goes unseen, and the thread looks done. To ask the user something, use the harness's question tool so the thread shows that it is waiting:
AskUserQuestion
in Claude Code,
request_user_input
in Codex, or the question tool your harness has. Put all the context in the question: the PR link, what blocks you, and the options with your recommendation first.
Ask only when you cannot continue alone:
  • You cannot prove the change.
  • The merge gate cannot pass, and you cannot fix that yourself.
  • The next step is outside the grant above: deleting data, touching production, changing things outside the repo, closing a PR, or force-pushing any other branch.
  • The goal is ambiguous in a way that changes the result.
  • Another PR makes this one obsolete.
Decide everything else yourself with sensible defaults, and list those decisions in the report.
If no question tool is available, or the tool returns no answer, take the safe path: leave the PR open and unmerged, and start your final message with the question.
在普通消息中提问会被忽略,而且 thread 看起来像是已完成。要询问用户,请使用 harness 的 question tool,让 thread 显示它正在等待:在 Claude Code 中是
AskUserQuestion
,在 Codex 中是
request_user_input
,或使用你的 harness 提供的 question tool。
在问题中包含所有上下文:PR 链接、阻塞原因和可选方案,并将推荐选项放在首位。
仅在无法独立继续时询问:
  • 无法证明变更。
  • merge gate 无法通过,且你无法自行修复。
  • 下一步不在上述授权范围内:删除数据、操作 production、修改 repo 之外的内容、关闭 PR,或 force-push 其他任何分支。
  • 目标存在足以改变结果的歧义。
  • 另一个 PR 使该 PR 失去必要性。
其他所有事项都由你采用合理默认值自行决定,并在 report 中列出。
如果没有可用的 question tool,或者工具未返回答案,请采取安全路径:将 PR 保持为 open 且 unmerged,并在最终消息开头提出问题。