Back to Details

tk-pr-open

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Open a PR

打开PR

Start when the intent to create or update one 
PR
is explicit, such as 
/tk-pr-open
, 
$tk-pr-open
, selection through the host skill picker, or “현재 브랜치로 PR 열어줘”.
The input is an already implemented and verified current-branch 
commit
. If a prepared 
.tigerkit/seed.md
exists, read the work 
goal
, 
acceptance
, and 
browser evidence requirement
, but the 
Seed
itself does not grant publication authority.
Do not repeat implementation, create a 
worker
, or add product 
commit
s. template 선택 또는 remote publication approval이 필요하면 host별 native structured question surface를 우선 사용합니다 (Claude Code: AskUserQuestion; Codex: request_user_input; Hermes: clarify). unavailable하면 같은 approval packet을 plain chat으로 fallback하고 exact current-turn approval 전 remote write를 하지 않습니다.
当明确有创建或更新一个
PR
的意图时启动，例如输入
/tk-pr-open
、
$tk-pr-open
、通过宿主技能选择器选择，或者说出“用当前分支打开PR”。
输入内容为已实现并验证的当前分支
commit
。 如果存在已准备好的
.tigerkit/seed.md
文件，读取其中的工作
目标
、
验收标准
和
浏览器证据要求
，但
Seed
本身不具备发布权限。
请勿重复执行实现操作、创建
worker
或添加产品
commit
。 如果需要选择模板或获得远程发布批准，请优先使用对应宿主的原生结构化提问界面（Claude Code：AskUserQuestion；Codex：request_user_input；Hermes：clarify）。若该界面不可用，则退化为用普通聊天形式发送相同的批准请求包，并且在获得当前轮次的明确批准前，不得执行远程写入操作。

Current state

当前状态

First, verify the following.
  • Repository and authenticated GitHub account
  • Current branch and 
    HEAD
  • Base branch
  • Target 
    commit
    and changed paths
  • 같은 
    head
    의 기존 
    PR
    존재 여부와 
    observed draft | ready
    상태
  • Unrelated dirty/staged paths
  • Target repository's 
    PR template
If the exact current 
commit
cannot be proven or unrelated changes are mixed in, do not broaden scope; return 
Blocked
/
Unverifiable
.
首先，验证以下内容：
  • 仓库和已认证的GitHub账户
  • 当前分支和
    HEAD
  • 基准分支
  • 目标
    commit
    和变更路径
  • 是否存在同一
    head
    的现有
    PR
    及其
    已观察到的草稿 | 就绪
    状态
  • 无关的未暂存/已暂存路径
  • 目标仓库的
    PR template
如果无法验证当前确切的
commit
，或者混入了无关变更，请不要扩大范围，返回
Blocked
/
Unverifiable
。

PR template

PR template

Before creating the 
PR body
, check supported template locations on the default branch.
  • Root
  • docs/
  • .github/
  • PULL_REQUEST_TEMPLATE/
    under each location
If exactly one template applies, preserve its heading order, checklists, HTML comments, and required sections. If multiple templates exist and there is no basis for choosing one, explain the candidates with one recommendation and ask the user to choose before publication approval. If the template cannot be read, do not invent a body.
在创建
PR body
之前，检查默认分支上支持的模板位置：
  • 根目录
  • docs/
    目录
  • .github/
    目录
  • 上述每个目录下的
    PULL_REQUEST_TEMPLATE/
    目录
如果恰好有一个模板适用，请保留其标题顺序、检查清单、HTML注释和必填部分。 如果存在多个模板且没有选择依据，请列出候选模板并给出一个推荐，然后在发布前请求用户选择。 如果无法读取模板，请不要自行编写PR正文。

Evidence

证据

Determine whether 
PR evidence
is needed from the prepared 
Seed
or the currently verified work.
text
required | optional | N/A | undecided
If a prepared 
Seed
marks 
tk-browser-verify
screenshot evidence as required for 
browser-visible acceptance
, use only validly inspected evidence. Approved 
tk-prototype
evidence may also be used.
Do not upload actual secret-bearing screenshots or unverified captures. If an image is required, pass the exact evidence path to 
tk-github-image-upload-to-pr
after the 
PR
exists.
根据已准备好的
Seed
或当前已验证的工作，确定是否需要
PR evidence
。
text
required | optional | N/A | undecided
如果已准备好的
Seed
标记
tk-browser-verify
截图证据为
浏览器可见验收
的必填项，则仅使用经过有效检查的证据。 已批准的
tk-prototype
证据也可使用。
请勿上传包含机密信息的截图或未经验证的捕获内容。 如果需要图片，请在
PR
创建完成后，将确切的证据路径传递给
tk-github-image-upload-to-pr
。

Publication plan

发布计划

Maintain 
.tigerkit/pr-open.md
as this skill's independent publication plan. Record and reread the following exact information.
text
Repository
PR operation: create | update
PR state: draft | ready
Base
Head ref + SHA
Push refspec
Title
Body
Template source/compliance
PR evidence requirement/state
Evidence producer/path
Known exclusions
This artifact owns only the current 
PR
publication plan, not the product work plan or 
worker
state. 새 
PR
은 사용자가 
draft
를 명시할 때만 
draft
로 만들고, 상태를 명시하지 않으면 기존 
ready
동작을 유지합니다. 기존 같은 
head
의 
PR
은 상태 변경 요청이 없으면 
fresh-read
한 상태를 보존합니다.
Present the following naturally to the user instead of hiding information behind a file they must open.
  • 포함되는 변경 요약
  • 정확한 제목/본문 또는 중요한 템플릿 섹션
  • 기준/헤드
  • 유효 
    PR state
  • 검사/증거 상태
  • 제외 범위/위험
  • 한 가지 발행 추천
将
.tigerkit/pr-open.md
作为本技能的独立发布计划进行维护。 记录并重新读取以下确切信息：
text
Repository
PR operation: create | update
PR state: draft | ready
Base
Head ref + SHA
Push refspec
Title
Body
Template source/compliance
PR evidence requirement/state
Evidence producer/path
Known exclusions
该文件仅负责当前
PR
的发布计划，不涉及产品工作计划或
worker
状态。 只有当用户明确指定为
draft
时，新
PR
才会以草稿形式创建；若未指定状态，则保持原有的
ready
状态逻辑。 对于同一
head
的现有
PR
，若无状态变更请求，则保留其最新读取的状态。
请自然地向用户展示以下信息，而不是将信息隐藏在需要用户打开的文件中：
  • 包含的变更摘要
  • 确切的标题/正文或重要的模板部分
  • 基准/头部分支
  • 有效的
    PR state
  • 检查/证据状态
  • 排除范围/风险
  • 一个发布建议

🔴 CHECKPOINT · 🛑 STOP · Publication boundary

🔴 检查点 · 🛑 停止 · 发布边界

Before any remote write, reread the plan and obtain one exact current-turn approval; do not treat the natural-language request “PR 열어줘” itself as publication approval. 승인에는 유효 
PR state
도 포함합니다. STOP if the plan, approved 
commit
, template/evidence state, or current repository state cannot be reverified.
在执行任何远程写入操作之前，请重新读取计划并获得当前轮次的明确批准；请勿将自然语言请求“打开PR”本身视为发布批准。批准内容还需包含有效的
PR state
。 如果无法重新验证计划、已批准的
commit
、模板/证据状态或当前仓库状态，请停止操作。

Publication

发布

After approval, recheck the repository, account, branch, 
HEAD
, base, existing 
PR
, and template source. 기존 
PR
의 
actual state
가 승인된 
plan
과 
material
하게 달라졌다면 승인을 무효화합니다. Invalidate the approval if any material 
drift
exists.
push
only the exact approved 
refspec
, and create or update only the specified 
PR
. 
Create
에서는 승인된 
PR state
를 적용하고, 
update
에서는 명시적으로 승인된 경우에만 상태를 변경합니다. Do not 
merge
, 
close
, 
tag
, or 
release
.
After creating or updating the 
PR
, reread the remote 
PR
and verify its URL, 
head SHA
, actual 
draft | ready
state, template compliance, and evidence state. If evidence is required, use the image uploader after the 
PR
exists. If the 
PR
was created but the required evidence upload fails, preserve the actual remote state and report completion as 
Blocked
.
获得批准后，重新检查仓库、账户、分支、
HEAD
、基准分支、现有
PR
和模板来源。 如果现有
PR
的
实际状态
与已批准的
计划
存在实质性差异，则作废批准。 若存在任何实质性
drift
（偏差），则作废批准。
仅推送确切的已批准
refspec
，并仅创建或更新指定的
PR
。 在
创建
操作中应用已批准的
PR state
；在
更新
操作中，仅当明确获得批准时才更改状态。 请勿执行
merge
、
close
、
tag
或
release
操作。
创建或更新
PR
后，重新读取远程
PR
并验证其URL、
head SHA
、实际
草稿 | 就绪
状态、模板合规性和证据状态。 如果需要证据，请在
PR
创建完成后使用图片上传工具。 如果
PR
已创建但必填证据上传失败，请保留实际的远程状态，并将完成状态报告为
Blocked
。

Completion

完成

사용자에게 중요한 결과만 보여줍니다.
  • PR
    URL
  • 생성/업데이트 여부
  • 현재 
    head
  • 현재 
    PR state
  • 검증/증거 결과
  • 남은 차단 요인
Do not show provenance dumps or product implementation receipts.
仅向用户展示重要结果：
  • PR
    URL
  • 是否创建/更新
  • 当前
    head
  • 当前
    PR state
  • 验证/证据结果
  • 剩余的阻塞因素
请勿展示来源转储或产品实现回执。