merge-to-prod

Name: merge-to-prod
Availability: InStock
Author: tobilafinhangit

Automate merge preparation and PR creation from Fizzy board data and Git history.

2|Updated Feb 2, 2026

Search Tags:#merge preparation #automated auditing #Git history #PR creation #Fizzy board

Ready to run

npx skills add https://github.com/tobilafinhangit/skill-master --skill merge-to-prod

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: merge-to-prod
Source: https://github.com/tobilafinhangit/skill-master/tree/main/.agent/skills/merge-to-prod
Command: npx skills add https://github.com/tobilafinhangit/skill-master --skill merge-to-prod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying, auditing, and preparing Pull Requests for tickets ready to be merged into production from a Fizzy board, saving time and reducing errors.

Core Features & Use Cases

Merge Preparation: Automatically detects and updates staging→main Pull Requests covering all cards in the "Merge to Prod" column.
Audit & Flag: Audits against Git history, flags shipped cards for closure and premature cards for move-back.
PR Creation: Drafts a PR title and body with all relevant cards and Infra changes, ready for review.

Quick Start

Run /merge-to-prod to audit cards and prepare a PR for merge to production.

Frequently Asked Questions about merge-to-prod

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

FAQPage Schema

How do I automate merge preparation and PR creation for tickets ready for production?▼

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.

What is the best way to audit Fizzy board cards against Git history before merging to production?▼

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.

Do I need API access to use automated auditing for Fizzy board staging to main merges?▼

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.

How does PR creation work for multiple Fizzy cards in the Merge to Prod column?▼

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.

Can I automatically flag shipped or premature tickets during merge preparation?▼

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.

What limitations exist when detecting staging to main branches for Fizzy board merges?▼

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.