Capgo Release Workflows

If you're running a Capacitor app and want to unify OTA updates through Capgo with your own CI/CD for native builds and store publishing, this skill acts as the top-level router across three workflow areas: live updates, native builds, and app store automation. It steps you through identifying what your release flow needs, then delegates to the specific skills for each piece while keeping signing, versioning, and rollback strategy under repository control. The real value is in the verification step at the end, where you confirm the whole chain works in order before production traffic hits it. It won't help if you're migrating Ionic Enterprise plugins or working outside the Capacitor ecosystem.

skills.sh installs: 749
GitHub stars: 77
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capgo-skills --skill capgo-release-workflows --agent claude-code

Installs into .claude/skills of the current project.

Files

Capgo Release Workflows

Set up an end-to-end release system: Capgo OTA for web changes, native builds for binary changes, store publishing, and a CI gate that picks the right path.

When to Use

TRIGGER when:

The user wants a single release pipeline covering live updates, native builds, and store publishing.
The user is moving off a hosted release service (Appflow-style) to CI they own.
The user asks "how does CI know if this needs a store release?"

Do not use when:

The user needs one operation (upload or promote a bundle, request one build). Use capgo-release-management or capgo-native-builds.
The user is wiring the updater plugin. Use capgo-live-updates.
The user is migrating off Ionic Appflow specifically. Start with ionic-appflow-migration, then return here for the pipeline.
The app is not Capacitor.