takeover

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Takeover

接管

Take responsibility for finishing the original goal while preserving the original contributors' credit. Do not defend an implementation just because another agent already built it.
Read the source PR, branch, or thread, including review findings and the user's later corrections. Resolve the handoff to the actual code and current head, and account for uncommitted work. Treat the handoff as context, not proof.
For a replacement PR, import the original commits onto a new branch and add your fixes separately. Honor an explicitly requested in-place or stacked continuation instead. Do not overwrite unrelated work or change the original PR without authorization.
Preserve Git authorship and existing co-author trailers. Credit the original contributors in the PR description and link the original PR when there is one. If the work will be squashed, preserve human author/co-author credit in the merge commit too, using verified identities rather than guessed emails. Model attribution is not a substitute for contributor credit.
Use
modernize
to update the continuation against its intended base and current architecture. Rework what is necessary to finish the same goal, not unrelated features. Simplify the implementation without dropping intended behavior or surfaces. Recheck the source PR too: it may have improved while you were working.
Independently verify the original failure and realistic workflows, following repository guidance and permissions. Green mocked tests do not prove the user experience works. State what remains unverified.
When the requested finish includes a PR, use
file-pr
to file or update it, then
babysit-pr
rather than stopping at creation. Use
leaving-pr-comments
for replies. Merge or close the original PR only when authorized.
Report what you inherited, what you changed, how you verified it, how credit was preserved, and any remaining decision.
负责完成原始目标,同时保留原有贡献者的署名。不要仅仅因为另一个 Agent 已经实现了某项功能,就为该实现辩护。
阅读源 PR、分支或线程,包括审查发现和用户后续提出的修正。将交接内容与实际代码和当前 HEAD 进行核对,并妥善处理未提交的工作。应将交接信息视为上下文,而不是证据。
如果要创建替代 PR,请将原有提交导入新分支,并单独添加你的修复。如果用户明确要求原地延续或堆叠式延续,则遵从该要求。未经授权,不要覆盖无关工作,也不要修改原始 PR。
保留 Git 作者信息和现有的共同作者尾注。在 PR 描述中注明原始贡献者;如果存在原始 PR,请链接到该 PR。如果工作最终会被压缩合并,也要在合并提交中使用经过验证的身份保留人类作者和共同作者署名,不要猜测邮箱。模型署名不能替代贡献者署名。
使用
modernize
根据预期的基础分支和当前架构更新延续后的工作。只重构完成同一目标所必需的部分,不要添加无关功能。可以在不丢失预期行为或功能入口的前提下简化实现。还要重新检查源 PR,因为在你工作期间,它可能已经有改进。
按照仓库的指导和权限,独立验证原始故障及实际使用流程。模拟测试全部通过并不能证明用户体验正常。应明确说明仍未验证的内容。
如果请求完成的任务涉及 PR,请使用
file-pr
创建或更新 PR,然后使用
babysit-pr
,不要在创建 PR 后直接停止。使用
leaving-pr-comments
回复评论。只有获得授权时,才合并或关闭原始 PR。
报告你接手了什么、修改了什么、如何进行了验证、如何保留了贡献者署名,以及还有哪些事项需要决策。