// 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.
| 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. |
Server-side merge of main → production using the GitHub merges API. No local checkout, no working tree changes.
.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:
git checkout production && git pull
git merge main # resolve conflicts in editor
git push origin production
SYNC_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 caseAdd, update, or remove text/image/video/audio/embeddings models. Covers the full lifecycle: files to touch, what to verify, and how to test empirically before merging.
Detect and analyze abusive accounts on Pollinations. IP clustering, multi-signal scoring, ban recommendations. Use when investigating abuse, bot farms, or suspicious usage patterns.
Debug and diagnose model errors in Pollinations services. Analyze logs, find error patterns, identify affected users. For taking action on user tiers, see tier-management skill.
Query billing, usage, credits, and resource deployments across all our cloud and SaaS providers (Azure, AWS, Cloudflare, GCP, Tinybird, Vercel, Stripe, Polar, etc.) via their native CLIs and APIs. Use for any question about provider costs, spend by service/day/month, credit eligibility, invoice totals, which resources are running, or how to deploy/inspect resources. Each provider has a dedicated playbook under `providers/`.
Analyze Pollinations revenue, pack purchases, and tier spending patterns. Query Polar for payment history and Tinybird for usage data.
Deploy Tinybird pipes and datasources for enter.pollinations.ai observability. Validates and pushes changes to Tinybird Cloud.