Open a PR
Start when the intent to create or update one
is explicit, such as
,
, selection through the host skill picker, or “현재 브랜치로 PR 열어줘”.
The input is an already implemented and verified current-branch
.
If a prepared
exists, read the work
,
, and
browser evidence requirement
, but the
itself does not grant publication authority.
Do not repeat implementation, create a
, or add product
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를 하지 않습니다.
Current state
First, verify the following.
- Repository and authenticated GitHub account
- Current branch and
- Base branch
- Target and changed paths
- 같은 의 기존 존재 여부와 상태
- Unrelated dirty/staged paths
- Target repository's
If the exact current
cannot be proven or unrelated changes are mixed in, do not broaden scope; return
/
.
Before creating the
, check supported template locations on the default branch.
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.
Evidence
Determine whether
is needed from the prepared
or the currently verified work.
text
required | optional | N/A | undecided
If a prepared
marks
screenshot evidence as required for
browser-visible acceptance
, use only validly inspected evidence.
Approved
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
exists.
Publication plan
Maintain
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
publication plan, not the product work plan or
state.
새
은 사용자가
를 명시할 때만
로 만들고, 상태를 명시하지 않으면 기존
동작을 유지합니다.
기존 같은
의
은 상태 변경 요청이 없으면
한 상태를 보존합니다.
Present the following naturally to the user instead of hiding information behind a file they must open.
- 포함되는 변경 요약
- 정확한 제목/본문 또는 중요한 템플릿 섹션
- 기준/헤드
- 유효
- 검사/증거 상태
- 제외 범위/위험
- 한 가지 발행 추천
🔴 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. 승인에는 유효
도 포함합니다.
STOP if the plan, approved
, template/evidence state, or current repository state cannot be reverified.
Publication
After approval, recheck the repository, account, branch,
, base, existing
, and template source.
기존
의
가 승인된
과
하게 달라졌다면 승인을 무효화합니다.
Invalidate the approval if any material
exists.
only the exact approved
, and create or update only the specified
.
에서는 승인된
를 적용하고,
에서는 명시적으로 승인된 경우에만 상태를 변경합니다.
Do not
,
,
, or
.
After creating or updating the
, reread the remote
and verify its URL,
, actual
state, template compliance, and evidence state.
If evidence is required, use the image uploader after the
exists.
If the
was created but the required evidence upload fails, preserve the actual remote state and report completion as
.
Completion
사용자에게 중요한 결과만 보여줍니다.
- URL
- 생성/업데이트 여부
- 현재
- 현재
- 검증/증거 결과
- 남은 차단 요인
Do not show provenance dumps or product implementation receipts.