merge-to-prod

Automate merge preparation by detecting staging→main branches and drafting PRs for all cards in the Merge to Prod column on a Fizzy board. The Skill audits Git history and compiles relevant cards and Infra changes into a ready PR.

Audit Fizzy board cards against Git history to identify discrepancies before merging to production. The process flags shipped cards for closure and premature cards for move-back, ensuring the staging→main PR only contains valid updates.

Yes, you need access to both the Fizzy API and your Git repositories to use automated auditing. This access allows the Skill to read board data, detect staging→main branches, and audit Git history for PR preparation.

PR creation works by aggregating all cards in the Merge to Prod column and generating a unified staging→main PR. It drafts a comprehensive title and body that lists all relevant cards and Infra changes, making the PR ready for review.

Yes, you can automatically flag tickets during merge preparation by auditing Git history. The Skill identifies shipped cards for closure and premature cards for move-back, preventing invalid or already completed work from entering the production PR.

The primary limitation is the strict dependency on Fizzy API and Git repository access, meaning the process cannot run without these integrations. Also, branch detection logic is restricted to the staging→main pattern.