Back to Details

ds-ship

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Own the work from its current state to a merged PR while nobody is watching.
Only act this way when the user clearly asked for it. The request grants three things: run the tests and app checks the proof needs without asking first, force-push this task's own branch with 
--force-with-lease
, and merge once the gate below passes. It grants nothing else.
在无人看管的情况下，从当前状态接手工作，直到 PR 合并。
只有在用户明确提出此要求时，才以这种方式行动。该请求授予三项权限：无需事先询问即可运行 proof 所需的测试和应用检查；使用 
--force-with-lease
强制推送此任务自己的 branch；并在下方 merge gate 通过后进行合并。除此之外，不授予任何权限。

Steps

步骤

  1. If you are on the default branch, create a new branch.
  2. Make the smallest change that meets the goal. Fix the case that was reported, not every case that might exist.
  3. Prove every part of the diff. Reproduce the failure, apply the fix, and run the same reproduction again. Run the checks CI runs. For UI or runtime behavior, run the app and look. Paste the command and its output into your notes.
  4. Review the change with 
    ds-review-loop
    . Re-prove anything the review changed.
  5. Rebase on the latest default branch, then file the PR with 
    ds-pr
    . Add one line that says how you proved it.
  6. Watch the PR with 
    ds-watch-pr
    . Fix real findings and CI failures, prove each fix, push, and watch again.
  7. Check the merge gate on the latest commit. Merge with the repo's usual method. Never use 
    --admin
    or any other bypass.
  8. Report the PR link, merge commit, proof, and every decision you made for the user.
Merge gate, all true on the latest head: proof covers the full diff, required checks are green, review bots are finished, each finding is fixed or answered with a reason, no human review asks for changes, and the branch is current and mergeable.
  1. 如果你当前位于 default branch，请创建一个新 branch。
  2. 进行满足目标的最小改动。修复已报告的情况，而不是修复所有可能存在的问题。
  3. 证明 diff 的每个部分。复现 failure，应用 fix，然后再次运行相同的复现步骤。运行 CI 会运行的 checks。对于 UI 或 runtime 行为，要运行应用并实际查看。将命令及其输出粘贴到 notes 中。
  4. 使用 
    ds-review-loop
    审查变更。对审查造成的任何改动重新进行 proof。
  5. 基于最新的 default branch 执行 rebase，然后使用 
    ds-pr
    创建 PR。添加一行说明你是如何完成 proof 的。
  6. 使用 
    ds-watch-pr
    监控 PR。修复真实的 findings 和 CI failures，对每次修复进行 proof，推送，然后再次监控。
  7. 在最新 commit 上检查 merge gate。使用仓库惯常的方法合并。绝不使用 
    --admin
    或任何其他绕过方式。
  8. 向用户报告 PR link、merge commit、proof 以及你做出的每一项决定。
Merge gate：在最新 head 上，以下条件必须全部为 true：proof 覆盖完整 diff，required checks 全部为 green，review bots 已完成，每个 finding 都已修复或已给出理由，没有 human review 要求修改，并且 branch 是最新且可合并的。

Stop when

何时停止

  • The PR is merged and the report is written.
  • You cannot prove the change, or the gate cannot pass and you cannot fix it. Ask the user.
  • The next step deletes data, touches production, closes a PR, or pushes another branch. Ask the user.
  • Six fix-and-watch cycles pass without a green gate. Stop and report what blocks it.
  • PR 已合并且 report 已写完。
  • 你无法 proof 变更，或者 merge gate 无法通过且你无法修复。此时询问用户。
  • 下一步会删除数据、触及 production、关闭 PR 或推送其他 branch。此时询问用户。
  • 经过六轮 fix-and-watch 循环仍未得到 green gate。停止并报告阻塞原因。

Rules

规则

  • Do not end your turn while checks are pending. Wait with the watcher.
  • Ask with the harness question tool, not a plain message. Put the PR link, the blocker and your recommended option in the question.
  • If no question tool exists or nobody answers, leave the PR open and unmerged, and start your final message with the question.
  • Evidence is output you saw in this session. A claim without output is not proof.
  • Keep scope fixed. Decline extra work from reviews and list it as follow-ups.
  • checks 尚在 pending 时，不要结束当前 turn。使用 watcher 等待。
  • 使用 harness question tool 提问，不要发送普通消息。在问题中附上 PR link、blocker 和你建议的 option。
  • 如果不存在 question tool，或者无人回答，则保持 PR 处于 open 且 unmerged 状态，并以问题作为最终消息的开头。
  • Evidence 必须是本次 session 中实际看到的 output。没有 output 的 claim 不算 proof。
  • 保持 scope 固定。拒绝 reviews 中提出的额外工作，并将其列为 follow-ups。