AGENT SKILL

pipeliner-release-production

Release the exact approved candidate to Production using the configured strategy, verify it, and recover safely on failure.

License 许可
MIT
最近更新
2026-11-12
Stars
★ 0
Forks
0

01 前言 Front Matter

name
pipeliner-release-production
description
Release the exact approved candidate to Production using the configured strategy, verify it, and recover safely on failure.

02 资源文件 1

03 SKILL.md 正文

Release Production

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: acknowledge approval for the owning Issue, configured release gate, and exact candidate. Report release results and remaining PM Testing against that Issue, with pull-request and deployment evidence as supporting details. Preserve the configured approval phrase.

Read AGENTS.md, pipeliner.config.json, the active Issue, approved candidate evidence, merged pull request when required, current Production state, and the matching section of release strategies.

  1. Require an actual configured role=production destination; none and native-only delivery skip this skill, including a multi-environment cycle whose final kind=production phase is native Stable distribution. With a cycle, require the production phase and Release Issue, completed preceding phase gates, aggregate pre-release QA/Showcase, frozen scope readiness and verified forward-ports under the cycle contract. Development-Issue integration and non-Production phase advancement do not invoke this skill. Revalidate the actual configured Production authorization against pre-release identity, pull-request state, exact reviewed tree, checks and environment immediately before mutation. This authorization is separate from final production-phase approval: do not require evaluatePhase to report production ready before deployment, because it needs final identity and post-deployment aggregate evidence. Link a resulting merge commit to the approved head/tree explicitly. Require pre-release local QA turns and cleanup complete; QA ownership is independent of deployment topology. Do not require future deployment IDs or interpret completion wording as pre-deployment acceptance. Do not create an artificial staging gate for direct Production.
  2. Record the current known-good Production source, artifact, configuration, deployment revision, data backup or integrity evidence, and non-destructive rollback procedure.
  3. For immutable promotion, prove Production receives the approved review digest without rebuilding. For direct Production, deploy the exact clean configured production-phase branch revision (default branch without a cycle). For multi-environment, require all configured candidate validations before integration or release.
  4. Use only configured build, promotion, deployment, and verification commands and the repository's declared source of truth. Application/native/image builds execute locally, never in Actions or transitive setup/quality workflows. Never make an imperative live edit the durable fix.
  5. Record the actual final release.candidateIdentity and its continuity from approved source/tree/artifact. Verify migrations, application health/readiness, restart counts, logs/events, service behavior, deployment controller state, and relevant platform health. Unknown final identity blocks completion.
  6. If verification fails, execute only the documented non-destructive rollback and verify recovery. Stop for PM authorization before destructive schema or data restoration.
  7. Record concise release evidence in the existing Issue or pull request. For a cycle, resume review for aggregate QA and every Human PM's final production-phase approval on the released identity, using the full release Showcase and exact evidence format; keep In Progress while turns/cleanup are pending, then In Review. Final phase approval does not replace configured completion acceptance. Resume pipeliner-close-issue with the actual next gate after verification; no repeated review trigger is needed. Feedback stays on the owning Issue with a fresh PR routed into governed development/stabilization, never a production feature/fix branch.

Production health does not equal PM acceptance. Do not close the Issue from this skill.

04 同仓库更多 Skills