Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -57% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 6% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -12% | 0% |
Server-side merge of main → production using the GitHub merges API. No local checkout, no working tree changes.
bash.claude/skills/sync-production/scripts/sync-production.sh
origin/main and origin/productiongit merge-tree (no working tree touched)POST /repos/pollinations/pollinations/merges to create the merge commit on production server-side0 — merge succeeded, or nothing to merge2 — merge would conflict (paths printed)3 — GitHub merges API rejected the request (branch protection, missing branches, etc.)The skill stops and reports the conflicting files. Don't try to force it — surface the reason in chat and resolve manually:
bashgit checkout production && git pull git merge main # resolve conflicts in editor git push origin production
bashSYNC_REPO=owner/repo SYNC_BASE=staging SYNC_HEAD=main \ .claude/skills/sync-production/scripts/sync-production.sh
gh (authenticated, push access to production) and jqproduction that requires PRs will cause exit code 3 — open a PR manually with gh pr create --base production --head main in that caseOther measured skills in the registry, with their headline benchmark lift.