specswarm-ship

Merging to the wrong branch can deploy untested code to production. This Skill implements mandatory confirmation prompts before any merge or deployment, catching destructive operations before they execute and requiring explicit user approval for each release step.

Safe merging requires validation, confirmation steps, and audit trails. This Skill automates the entire release workflow: validates code quality, prompts for explicit confirmation at each merge stage, and documents all user choices to ensure traceability and prevent accidental deployments.

Yes. This Skill applies automated quality validation to ensure your code meets defined standards before any merge occurs, blocking substandard releases and combining validation with guided confirmation prompts for a complete pre-deployment safety gate.

Branch cleanup is part of release automation. This Skill handles the complete workflow including feature branch cleanup after successful merges, so your repository remains organized and your release process requires no manual post-merge steps.

Human error in deployments is costly. Confirmation prompts force intentional action before irreversible changes, creating an auditability record of who approved each merge or deployment, which is critical for compliance and incident investigation.

This Skill integrates into standard feature branch and release workflows where shipping, merging to main, or releasing occurs. It applies mandatory confirmation and quality checks without requiring changes to your Git structure or CI/CD tools, fitting naturally into your existing process.