ds-adopt

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Finish someone else's work as if it were yours, but credit them for what they did.

完成他人所做的工作，就如同这是你自己完成的一样，但必须为对方已有的贡献保留署名。

Read the source PR, branch or thread in full: description, commits, review comments and any later corrections from the user.
Find the real current state: the head SHA, uncommitted changes and open review findings. Treat the handoff notes as hints, not facts.
Write down the original goal in one sentence.
Choose where to work. By default, make a new branch with the original commits on it and add your fixes as separate commits. Continue in place or stack only if the user asked for it.
Run
```
ds-revive
```
to bring the work up to date with the base branch.
Fix what is needed to reach the original goal. Simplify where you can, but keep every intended behavior.
Verify on your own. Reproduce the original problem, then show it fixed. Run the real workflow, not only mocked tests. Record the commands and output.
Check the source PR again. It may have changed while you worked.
If a PR is wanted, file it with
```
ds-pr
```
, then watch it with
```
ds-watch-pr
```
. Use
```
ds-pr-comments
```
for any reply.
Report what you inherited, what you changed, how you verified it, how credit was kept and what is still open.

完整阅读源 PR、分支或线程：描述、commits、review comments，以及用户之后提出的任何修正。
查明当前的真实状态：head SHA、未提交的更改和尚未解决的 review 意见。应将交接说明视为提示，而非事实。
用一句话写下原始目标。
选择工作位置。默认创建一个新分支，将原有 commits 保留在该分支上，并将你的修复作为单独的 commits 提交。除非用户明确要求，否则应原地继续或使用 stack。
运行
```
ds-revive
```
，使工作内容与基础分支保持同步。
修复达成原始目标所需的一切问题。可以在适当之处进行简化，但必须保留所有预期行为。
自行验证。先复现原始问题，然后展示修复结果。运行真实的工作流，而不只是 mocked tests。记录所用命令及其输出。
再次检查源 PR。它可能在你工作期间发生了更改。
如果需要创建 PR，请使用
```
ds-pr
```
提交，然后使用
```
ds-watch-pr
```
跟踪。需要回复时，使用
```
ds-pr-comments
```
。
报告你接手了什么、修改了什么、如何完成验证、如何保留署名，以及还有哪些问题尚未解决。

Keep the original Git authors and co-author trailers. Name the contributors and link the original PR in the description.
If the PR will be squashed, keep human co-author lines in the squash message. Use verified identities only, never guessed emails.
Do not defend the old code because it exists. Do not add unrelated features.
Do not edit, merge or close the original PR without permission.
State plainly what you could not verify.