Draft PR
Own end-to-end draft-PR publication after implementation, validation, and review are complete.
Workflow
- Confirm shipping authority, repository rules, base branch, remotes, current branch, exact scope, and completed validation and review evidence.
- Preserve unrelated staged, unstaged, and untracked work. Stop only when safe isolation is impossible or a scoped path is sensitive or unexpectedly generated.
- Create a short branch when needed, stage explicit paths with
git add -- <paths>, and review the staged path list and diff.
- Run required checks when existing evidence does not cover the exact staged content.
- Follow repository PR templates, title conventions, and required fields. Otherwise write concise evidence-based
Problem, Change, Tests, and only necessary Notes sections.
- Use
text-improve on the completed title and body without changing verified facts, required template wording, or technical terms.
- Use
change-cleanup-review on the complete staged change and proposed PR presentation. Stop and report material cleanup findings unless the parent request separately authorizes repair. After an authorized repair, restage the exact scope and rerun invalidated checks and prose improvement.
- Commit using repository conventions and push with an upstream when needed.
- Open a draft PR and monitor checks for the pushed commit.
- Diagnose failures from logs. Route behavior changes through
behavior-implement and test-design, and specialist failures through their owning workflow; verify, rerun change-cleanup-review when corrections materially move the change, then commit and push only scoped corrections.
- Stop when checks pass, the user permits cancellation, or a concrete external blocker prevents meaningful progress.
Do not rewrite history, force-push, merge, mark ready, release, weaken tests, disable validation, expose secrets, or override repository PR conventions.
Finish with the draft PR URL, commits, checks, final CI state, and blockers.
1---2name: pr-draft3description: Publish confirmed local changes as a monitored GitHub draft pull request. Use only when the user authorizes branch creation, scoped staging, commit, push, draft PR creation, and CI follow-up.4---56# Draft PR78Own end-to-end draft-PR publication after implementation, validation, and review are complete.910## Workflow11121. Confirm shipping authority, repository rules, base branch, remotes, current branch, exact scope, and completed validation and review evidence.132. Preserve unrelated staged, unstaged, and untracked work. Stop only when safe isolation is impossible or a scoped path is sensitive or unexpectedly generated.143. Create a short branch when needed, stage explicit paths with `git add -- <paths>`, and review the staged path list and diff.154. Run required checks when existing evidence does not cover the exact staged content.165. Follow repository PR templates, title conventions, and required fields. Otherwise write concise evidence-based `Problem`, `Change`, `Tests`, and only necessary `Notes` sections.176. Use `text-improve` on the completed title and body without changing verified facts, required template wording, or technical terms.187. Use `change-cleanup-review` on the complete staged change and proposed PR presentation. Stop and report material cleanup findings unless the parent request separately authorizes repair. After an authorized repair, restage the exact scope and rerun invalidated checks and prose improvement.198. Commit using repository conventions and push with an upstream when needed.209. Open a draft PR and monitor checks for the pushed commit.2110. Diagnose failures from logs. Route behavior changes through `behavior-implement` and `test-design`, and specialist failures through their owning workflow; verify, rerun `change-cleanup-review` when corrections materially move the change, then commit and push only scoped corrections.2211. Stop when checks pass, the user permits cancellation, or a concrete external blocker prevents meaningful progress.2324Do not rewrite history, force-push, merge, mark ready, release, weaken tests, disable validation, expose secrets, or override repository PR conventions.2526Finish with the draft PR URL, commits, checks, final CI state, and blockers.
yarlson