file-pr

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

File one concise, reviewable pull request with

gh

. The reader is Dustin (or a future second developer) skimming dozens of these — optimize for them.

使用

gh

提交一份简洁、便于评审的拉取请求（pull request）。审阅者是Dustin（或未来的第二位开发者），他们会快速浏览数十份这样的请求——请为他们优化内容。

Check whether a PR for this branch already exists:
```
gh pr list --head <branch>
```
. If yes, update that one instead of opening a second.
Review the diff against
```
origin/main
```
and confirm it matches the user's original goal — nothing more.
Branch names follow the repo convention:
```
feature/…
```
or
```
fix/…
```
.

PR titles usually become commit messages. One short line that explains why the change matters, in plain language.

Bad:

fix server parse CLI version in update pre-flight

Good:

fix: version drift warning showed on every start

PR标题通常会成为提交信息。用简短的一句话，以平实语言说明更改的重要性。

反面示例：

fix server parse CLI version in update pre-flight

正面示例：

fix: version drift warning showed on every start

Open with the problem in the user's words, then briefly the solution. Do not lead with an implementation inventory.

Bad: "Removed implicit workspace carryover from every new thread entry point. New threads inherit only the project from context…"
Good: "My new-worktree default was ignored when starting new threads. Super unintuitive. Now the preference always applies."

End with one line naming the model and harness that made the change, e.g.

— claude-fable-5 via T3 Code

. If the harness does not expose the model slug, say so instead of guessing.

开头用用户的原话说明问题，然后简要介绍解决方案。不要先罗列实现细节。

反面示例："Removed implicit workspace carryover from every new thread entry point. New threads inherit only the project from context…"
正面示例："我设置的new-worktree默认值在启动新线程时被忽略了，这非常不符合直觉。现在该偏好设置会始终生效。"

结尾用一行文字说明做出更改的模型和工具，例如

— claude-fable-5 via T3 Code

。如果工具未显示模型标识，请如实说明，不要猜测。

Open a real PR, not a draft — drafts skip review bots where they exist.
Never include secrets,
```
.env
```
contents, or customer paths in title or body.
Screenshots or recordings: upload via the
```
file-upload
```
skill and embed the URL. Never commit media into the repo for this.
If the user also said "babysit", continue with the
```
babysit-pr
```
skill after filing.

If the repository has no remote or the user normally commits straight to

main

, say so and offer a plain commit instead of inventing a PR flow.

如果仓库没有远程分支，或者用户通常直接提交到

main

分支，请告知用户并提议直接提交普通版本，而非创建PR流程。