Agent Skills › pollinations/pollinations › sync-production

sync-production

GitHub

负责将 main 分支同步至生产环境，涵盖创建/合并推广 PR、验证 Tinybird 数据源与 D1 迁移、处理 GitHub Actions 部署及最终版本验证，确保发布流程安全合规。

.claude/skills/sync-production/SKILL.md pollinations/pollinations

Trigger Scenarios

将 main 合并到 production 部署 main 到生产环境同步生产环境

Install

npx skills add pollinations/pollinations --skill sync-production -g -y

More Options

Non-standard path

npx skills add https://github.com/pollinations/pollinations/tree/main/.claude/skills/sync-production -g -y

Use without installing

npx skills use pollinations/pollinations@sync-production

指定 Agent (Claude Code)

npx skills add pollinations/pollinations --skill sync-production -a claude-code -g -y

安装 repo 全部 skill

npx skills add pollinations/pollinations --all -g -y

预览 repo 内 skill

npx skills add pollinations/pollinations --list

SKILL.md

Frontmatter

{
    "name": "sync-production",
    "description": "Promote Pollinations main to production through the required promotion PR and GitHub Actions. Use when asked to merge main into production, deploy main to production, or sync production."
}

Sync Production

Follow the Git workflow, production deployment, and secret-safety rules in root AGENTS.md.

Inspect current main and production revisions and the complete pending diff. Reuse an open main → production promotion 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. Follow tinybird-deploy for authorized changes.
Compare pending D1 migrations with production migration history. Verify that .github/workflows/deploy-cloudflare-production.yml applies 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 production as specified in AGENTS.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-services skill.