菜单
Use when implementation is verified and the branch must proceed through review, PR, merge, and cleanup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | finishing-a-development-branch |
| description | Use when implementation is verified and the branch must proceed through review, PR, merge, and cleanup. |
Canonical workflow: capability, ownership, state machine, states, gates, review packet, terminal runbook.
TPM is the coordinator/integrator for this sequence. Gate meanings, retry/disposition rules, merge authorization, and terminal order come only from the canonical links above.
Use after implementation and its required verification are complete.
git diff --check <Comparison Ref>...<Source Head>../scripts/prepare-task-pr.sh --draft-candidate --create and obtain a trusted ci_ready_receipt for its exact head.requesting-repo-owned-review; resolve findings against that same head../scripts/pm/task-closeout.sh --role <owner_role> --task-uid <TASK-UID> \
--comparison-ref "<Comparison Ref>" --verification-profile <repository-owned-profile> \
--review-packet-file <canonical-review-packet.json> --ci-ready-receipt <receipt.json>
Partial remote state recovers via refresh -> audit -> retry; do not edit cache JSON. 6. Promote the existing draft only through:
./scripts/prepare-task-pr.sh --promote-draft <receipt.json>
Pre-PR local role review packet recorded after immutable verification and before PR creation; its schema is only at the canonical review-packet link.
./scripts/pm/pr-lifecycle-gate.py <pr-number> --task-uid <task_uid> --json
./scripts/pr-review-thread-closeout.sh --unresolved-only
For a stable long-running required check or required-gate wait, follow the
canonical stable-wait rule.
On a non-Codex surface, use the finite fallback:
./scripts/pm/pr-watch-loop.sh <pr-number> --task-uid <task_uid>
Post-PR checks/comments/mergeability remain separate gates. All interpretations, retry loops, dispositions and merge authorization come from the canonical gate definitions, not this skill.
9. Merge only with trusted gate evidence and the gate-selected repository path.
A live MERGEABLE result with REVIEW_REQUIRED and approval-only BLOCKED
or informational BEHIND defaults to admin merge
when the gate emits use_admin_merge: true; do not request separate task or
user authorization. Any hold or substantive gate blocker still fails closed.
Do not land locally unless the user explicitly asks for local landing.
Missing trusted runtime attestation is capability_blocked for unattended
automation, not for the current human-operated PR path. Never manufacture a
passed packet or downgrade a real blocker to waiting.
Do not bypass a canonical gate, mutate implementation after freeze without restarting review, or clean up before trusted merge evidence.
Stale verification; locally fabricated receipts; treating PR creation as completion; cleanup against unbound paths.
Use when any oasis7 user request starts and must bind the canonical worktree, GitHub-backed task truth, and owner before routing.
Use when a branch is about to create a PR and needs fresh involved-role review.
Use when a task has written repo truth and implementation should proceed step by step with evidence.
Use when about to claim a task is complete, tests passed, a branch is ready for PR, or a PR is ready to merge. Requires fresh verification, direct output inspection, and use of `./scripts/pm/claim-ready.sh` when the claim can be mapped to one verification command.
Use when a bound oasis7 task needs the next repo-owned workflow phase selected.
Use when assessing or developing the blocked production-supervisor target for a bound oasis7 task spanning multiple lifecycle phases.