release-integration

Runs final integration checks and produces commit plans, PR drafts, and release handoff notes.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill release-integration-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-integration
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/release-integration
Command: npx skills add https://github.com/vovanostm-public/multica --skill release-integration-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a code change for release requires coordinating checks, security reviews, diff validation, and policy approvals, and skipping any of these steps risks shipping unverified or non-compliant work. ## Core Features & Use Cases - Changed Checks Verification: Runs or verifies recent test results and blocks the release when checks are red. - Commit and PR Planning: Prepares commit plans and PR drafts only when policy allows, with PR bodies linking back to evidence. - Release Handoff and Rollback Notes: Produces typed outputs including integration summaries, release handoffs, and rollback notes with evidence, assumptions, blockers, and confidence levels. - Use Case: After an implementation stage finishes, use this Skill to verify checks are green, confirm the security review is complete, and generate a reviewer-ready PR draft with rollback notes before handoff. ## Quick Start Run the release integration stage on the current worktree to verify checks, review the diff, and produce a commit plan, PR draft, and release handoff summary.

Frequently Asked Questions about release-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a PR draft after implementation checks pass?▼

Verify the changed checks are green, review the diff scope and secret scan status, then generate a commit plan and PR draft only if policy allows. The PR body must link back to the supporting evidence.

What should a release handoff summary include?▼

A release handoff should include the integration summary, changed check results, commit plan, PR draft, and rollback notes. Every output must also carry used evidence, assumptions, blockers, and a confidence level.

When should a release be blocked during final integration?▼

Block the release when checks are red, the diff contains unrelated changes, or a security review is missing for a risky change. A required wiki update must also have an update plan before the stage is marked done.

Can this stage merge or deploy code automatically?▼

No, it does not merge or deploy autonomously unless an explicit approved policy exists. Privileged actions must go through the approved action pipeline rather than being executed directly.

Why does release integration fail when evidence is missing?▼

The stage requires typed, stage-local evidence such as verification results and security reviews before producing outputs. Missing or untyped evidence blocks the handoff because downstream reviewers cannot validate the change.