Agent Skills
› pollinations/pollinations
› sync-production
sync-production
GitHub通过GitHub合并API将main分支同步至production,预检冲突并处理结果。
Trigger Scenarios
merge main into production
deploy main to production
sync production
Install
npx skills add pollinations/pollinations --skill sync-production -g -y
SKILL.md
Frontmatter
{
"name": "sync-production",
"description": "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."
}
Sync Production
Server-side merge of main → production using the GitHub merges API. No local checkout, no working tree changes.
Quick Usage
.claude/skills/sync-production/scripts/sync-production.sh
What It Does
- Fetches
origin/mainandorigin/production - Lists the commits that would be merged
- Pre-checks for conflicts with
git merge-tree(no working tree touched) - If conflicts → stops with the conflicting paths and exits non-zero. Resolve manually, then re-run.
- If clean → calls
POST /repos/pollinations/pollinations/mergesto create the merge commit onproductionserver-side
Exit Codes
0— merge succeeded, or nothing to merge2— merge would conflict (paths printed)3— GitHub merges API rejected the request (branch protection, missing branches, etc.)
On Conflict
The skill stops and reports the conflicting files. Don't try to force it — surface the reason in chat and resolve manually:
git checkout production && git pull
git merge main # resolve conflicts in editor
git push origin production
Overrides
SYNC_REPO=owner/repo SYNC_BASE=staging SYNC_HEAD=main \
.claude/skills/sync-production/scripts/sync-production.sh
Notes
- Run from repo root
- Requires
gh(authenticated, push access toproduction) andjq - Branch protection on
productionthat requires PRs will cause exit code3— open a PR manually withgh pr create --base production --head mainin that case
Version History
- 99bce92 Current 2026-07-25 10:39


