pipeliner-close-issue
Complete an active Issue only after exact-candidate release evidence and every configured PM Testing approval gate are current.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pipeliner-close-issue
- description
- Complete an active Issue only after exact-candidate release evidence and every configured PM Testing approval gate are current.
02 资源文件 1
- 参考文档agents/openai.yaml201 B
03 SKILL.md 正文
Close an Issue
Apply the shared installed repository home and message-only questions contracts. First adoption retains its explicit-target gate. When an answer is needed, ask in the final ordinary message and end the turn immediately; no work or tool calls follow until the Human replies.
Follow Issue-based communication: request and acknowledge completion for the owning Issue and exact candidate. The official response is Approved; identify the Issue, candidate and authorized outcome in the request. Final QA acceptance also authorizes closure when no distinct release-stage testing remains. Lead the final status with the Issue and report it complete only after every gate and live readback pass. Retain the linked pull request as supporting evidence.
Read AGENTS.md, pipeliner.config.json, the sole active Issue, matching pull request, candidate record, current PM approval, checks, release evidence, and live Project state.
Closure is the final step of the same feature-branch PR lane: PM feedback is remediated and re-tested on that candidate before approval; approval is bound to the exact PR head and does not authorize another Issue. Merge and Issue closure are separate verified readbacks, and a subsequent Issue requires an explicit PM call.
Apply the release-cycle contract before the simple strategy steps below when a cycle exists. A development Issue closes on its own exact-candidate paired QA, full Showcase, configured integration acceptance and verified phase-branch integration, with target/milestone linkage retained. Do not require Production for that Issue or imply aggregate release acceptance. For the Release Issue, verify aggregate all-pair/all-PM gates, frozen scope, blockers and forward-ports for completed phases; keep it open through final release acceptance. When an actual Production destination is configured, Production mutation requires separate pre-release authorization and invokes the Production skill before final phase evaluation. Otherwise a final kind=production phase may be native Stable distribution: prepare the native candidate, perform configured authorized distribution/integration and verify its actual final identity, then require aggregate QA, all-PM phase approval and completion acceptance. Do not invoke the Production skill or invent a service URL/deployment ID for native-only delivery. Use the phase's configured branch/approval/promotion rules in place of simple default-branch assumptions. All final cleanup and live readback requirements below still apply.
- Require In Review, successful configured gates, zero unresolved findings, stage-appropriate identity and the actual approval required next by the release strategy. Verify every local QA turn, exact PM approval and final cleanup using local QA execution. Pending turns return to review in In Progress; never invent completed turns or require an undeployed candidate's final identity before merge.
- Follow AGENTS.md's one-approval-per-tested-outcome rule. For none and native-only delivery without Production, all required PM QA approvals authorize exact-candidate integration and closure after verification and cleanup. Do not request a separate completion phrase. The Showcase must state this outcome; intermediate pair approvals only advance the baton. For strategies with Production, require configured Production authorization before merge/deploy. Bind approval to the pre-release candidate and use the exact head when merging. Verify the resulting integration-branch tree equals the reviewed tree and record the resulting source commit. Stop on mismatch; unrelated changes require fresh QA/approval.
- Invoke
pipeliner-release-productionyourself only when a configured Production destination is not yet verified. Skip it for none and native-only releases; verify source or native publication through the declared procedure instead. Do not rebuild an immutable candidate. - Where Production requires final PM Testing, keep the Issue open until that final acceptance covers the released identity; that approval also authorizes closure. For none and native-only delivery, the final required QA approval remains valid through the verified exact-candidate integration in step 2. Do not request an additional Issue approval or repeat a completed gate for the same unchanged candidate.
- Re-read applicable source, tree, artifact, deployment, approvals, Issue, card, and health immediately before completion. Unexpected identity change invalidates approval. Record the intended merge/deployment transition without transferring approval to a different tree or artifact.
- Only after every configured gate passes, merge the exact approved PR, verify the resulting integration-branch commit/tree and linked PR, then add concise evidence to the Issue or pull request, close the Issue, move its card to Done, clear assignment when policy requires it, delete the merged branch when safe, and read everything back. Do not close from a PR merely because it exists or is green.
- Verify zero active Issues and report the outcome with regression steps appropriate to the actual source/native/Production target. Do not invent Production for none or create a duplicate acceptance report. Do not start another Issue until the PM explicitly calls for it.
A merged pull request or healthy deployment alone is never completion.
04 同仓库更多 Skills
pipeliner-work-issue
Use the canonical workflow to start or resume one Issue and lead the next authorized stage.
pipeliner-update
Use the canonical workflow to update an existing Pipeliner adoption while preserving local configuration.
pipeliner-review-issue
Use the canonical workflow to resume review or feedback before or after merge and guide PM Testing.
pipeliner-release-production
Use the canonical workflow to release an approved candidate.
pipeliner-release-candidate
Use the canonical workflow to prepare an exact release candidate.
pipeliner-pipeline-health
Use the canonical workflow to audit pipeline health read-only.