sync-production
Automates the merge of main to production with conflict pre-checks.
Install
mkdir -p .claude/skills/sync-production && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14682" && unzip -o skill.zip -d .claude/skills/sync-production && rm skill.zipInstalls to .claude/skills/sync-production
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Sync the main branch into production via the GitHub merges API. Pre-checks for merge conflicts and bails out with a clear reason if the merge isn't clean. Use when asked to merge main into production, deploy main to production, or sync production.Key capabilities
- →Fetch `origin/main` and `origin/production` branches
- →List commits that would be merged
- →Pre-check for merge conflicts with `git merge-tree`
- →Create a merge commit on `production` server-side via GitHub API
- →Report conflicting paths if a merge would conflict
How it works
The skill fetches the latest `main` and `production` branches, then uses `git merge-tree` to pre-check for conflicts. If clean, it calls the GitHub merges API to create the merge commit server-side.
Inputs & outputs
When to use sync-production
- →Deploy main to production
- →Sync production with main branch
- →Check merge conflicts for production
About this skill
Sync Production
Follow the Git workflow, production deployment, and secret-safety rules in root AGENTS.md.
- Inspect current
mainandproductionrevisions and the complete pending diff. Reuse an openmain→productionpromotion PR, or create one for the requested promotion. - Check changed Tinybird datasources and pipes in the pending diff. Use bounded production queries and endpoint calls to verify the required schema in
pollinations_enter. Tinybird is deployed separately: missing resources or failed probes block promotion. Followtinybird-deployfor authorized changes. - Compare pending D1 migrations with production migration history. Verify that
.github/workflows/deploy-cloudflare-production.ymlapplies them before the affected Workers deploy, and that old Workers remain compatible during that interval. Record both data checks and any blockers in the promotion PR body. - Check the current PR head, required checks, conflicts, and deployment prerequisites. Merge through the PR when authorized and checks pass; resolve or report blockers within that workflow.
- Follow the resulting GitHub Actions deployments. When path filters do not trigger the required production workflow, dispatch it from
productionas specified inAGENTS.md. - Verify the deployed revision, required bindings, and affected behavior; report any incomplete verification.
- The production deploy re-pushes unchanged, already-approved secrets; that is not a rotation and needs no new approval. A new or changed value does. Per-Worker secret checks:
enter-servicesskill.
When not to use it
- →When `production` branch has protection that requires PRs
- →When the user wants to merge branches other than `main` into `production`
- →When the user wants to perform a local merge with working tree changes
Prerequisites
Limitations
- →Requires `gh` and `jq` to be installed.
- →Branch protection on `production` that requires PRs will cause the skill to exit.
- →The skill does not perform local checkouts or working tree changes.
How it compares
This skill performs a server-side merge of `main` to `production` via the GitHub API with pre-conflict checks, avoiding local working tree changes and providing a more automated and controlled deployment process than manual git operations.
Compared to similar skills
sync-production side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sync-production (this skill) | 0 | 4mo | Review | Intermediate |
| github-workflow-automation | 11 | 4mo | Review | Advanced |
| testing-workflow | 16 | 11mo | Review | Intermediate |
| github-actions-templates | 7 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by pollinations
View all by pollinations →You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
create-pr
n8n-io
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.