quick-send

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Quick Send

Quick Send

Do the same unattended work as
full-send
, but push the change straight to origin's default branch instead of filing a PR. The user is not watching this thread, so your updates and final message go unread until long after you stop.
Read full-send and follow its Testing permission, Proof, and Asking the user sections. Its PR steps (file, babysit, merge gate, merge) do not apply. The rules below take precedence.
The user grants you permission to:
  • Push this task's commits to origin's default branch as a fast-forward.
  • Use the test methods that Proof needs, without asking first.
执行与
full-send
相同的无人值守工作,但将变更直接推送到 origin 的默认分支,而不创建 PR。用户当前不会关注此线程,因此你的进度更新和最终消息要等到你结束工作很久之后才会被查看。
阅读 full-send,并遵循其中的 Testing permission(测试许可)、Proof(验证)和 Asking the user(询问用户)章节。其 PR 步骤(file、babysit、merge gate、merge)不适用。以下规则优先。
用户授予你以下权限:
  • 将本任务的提交以 fast-forward 方式推送到 origin 的默认分支。
  • 无需事先询问,即可使用 Proof 所需的测试方法。

Steps

步骤

  1. Find the default branch. Fetch origin and read its default branch (
    git symbolic-ref refs/remotes/origin/HEAD
    , or
    gh repo view --json defaultBranchRef
    ). It may be
    main
    ,
    master
    , or something else.
  2. Finish the change. Complete the goal from the user's request with the smallest change that works. Work on the local default branch, or on a branch when the checkout holds unrelated work, you are in a worktree, or a branch keeps things cleaner.
  3. Prove it. Get proof for every change you made.
  4. Get feedback. Use the
    sol-loop
    skill to verify changes. Re-prove any behavior a fix touches.
  5. Commit with the
    committing-with-guidelines
    skill. Commit only this task's changes; leave unrelated uncommitted work where you found it.
  6. Rebase onto the latest
    origin/<default>
    . If upstream moved, re-run the repo's CI checks on the rebased commit, and re-prove behavior a conflict fix touched.
  7. Push when the push gate passes:
    git push origin HEAD:<default>
    . If the push is rejected as non-fast-forward, return to step 6 and push again.
  8. Check CI. If the repo runs CI on pushes to the default branch, wait for the run on your commit (
    gh run watch <id> --exit-status
    ). When your change breaks it, fix forward with a new commit through steps 3 to 7.
  9. Report in your final message: the default branch, each pushed commit SHA, your proof, the CI result, and each decision you made for the user.
Stay active from step 1 to step 9. Ending your turn while CI is pending stops the work, because nobody will prompt you again.
  1. 找到默认分支。 获取 origin 并读取其默认分支(
    git symbolic-ref refs/remotes/origin/HEAD
    ,或
    gh repo view --json defaultBranchRef
    )。它可能是
    main
    、
    master
    或其他分支。
  2. 完成变更。 根据用户请求,以能够奏效的最小改动完成任务。在本地默认分支上工作;当 checkout 中存在无关工作、当前处于 worktree,或使用分支能让工作更清晰时,则在分支上工作。
  3. 验证变更。 为所做的每一项变更获取证明。
  4. 获取反馈。 使用
    sol-loop
    skill 验证变更。对于修复所触及的任何行为,重新进行验证。
  5. 提交,使用
    committing-with-guidelines
    skill。仅提交本任务的变更;不要提交无关的未提交工作,保持其原状。
  6. 变基到最新的
    origin/<default>
    。如果上游已有变动,则在变基后的提交上重新运行仓库的 CI 检查,并重新验证冲突修复所触及的行为。
  7. 推送,前提是推送门禁通过:
    git push origin HEAD:<default>
    。如果推送因非 fast-forward 被拒绝,则返回步骤 6 并再次推送。
  8. 检查 CI。 如果仓库在推送到默认分支时运行 CI,请等待该提交上的运行完成(
    gh run watch <id> --exit-status
    )。如果变更导致 CI 失败,则通过步骤 3 至 7 使用新提交向前修复。
  9. 报告。在最终消息中说明:默认分支、每个已推送提交的 SHA、你的验证结果、CI 结果,以及你替用户做出的每项决定。
从步骤 1 到步骤 9 保持活跃。如果在 CI 仍在等待时结束回合,工作就会停止,因为不会有人再次提示你。

Push gate

推送门禁

Push only when all of these are true on the rebased commit:
  • Your proof covers every change in
    git diff origin/<default>..HEAD
    .
  • sol-loop
    ended in agreement.
  • The repo's CI checks pass locally.
  • The commits hold only this task's changes.
  • The push is a fast-forward of
    origin/<default>
    .
Pushed history is shared: fix it forward with new commits. Never force-push the default branch, rewrite commits already on origin, or bypass branch protection. If origin rejects direct pushes (protected branch, required PR), ask the user, and offer
full-send
as the recommended option.
仅当变基后的提交满足以下所有条件时才能推送:
  • 你的证明覆盖
    git diff origin/<default>..HEAD
    中的每一项变更。
  • sol-loop
    已结束并达成一致。
  • 仓库的 CI 检查在本地通过。
  • 提交仅包含本任务的变更。
  • 推送是
    origin/<default>
    的 fast-forward。
已推送的历史记录是共享的:请通过新增提交向前修复。绝不 force-push 默认分支、重写 origin 上已有的提交,或绕过分支保护。 如果 origin 拒绝直接推送(受保护分支、要求 PR),则询问用户,并推荐使用
full-send
作为建议方案。

Asking the user

询问用户

Follow full-send's rules with these swaps: give the default branch and your local commits in place of a PR link, treat "the push gate cannot pass" as the merge gate case, and when no answer comes, leave the commits unpushed and start your final message with the question.
遵循 full-send 的规则,但进行以下替换:用默认分支和本地提交代替 PR 链接;将“推送门禁无法通过”视为合并门禁情形;当没有收到答复时,不推送提交,并以问题作为最终消息的开头。