release-preflight

Validate Flutter release readiness by checking version numbers, signing configurations, and store metadata.

6|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ImL1s/flutter-claude-skills --skill release-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-preflight
Source: https://github.com/ImL1s/flutter-claude-skills/tree/main/skills/release-preflight
Command: npx skills add https://github.com/ImL1s/flutter-claude-skills --skill release-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preflight checks help prevent release blockers by validating pubspec version/build numbers, signing configurations, and store metadata before any Flutter release.

Core Features & Use Cases

  • Version & Build Number validation: ensure pubspec and platform-specific build numbers are unique and incremented.
  • Signing and CI readiness: verify signing certificates, provisioning profiles, and Fastlane config are correct for iOS and Android.
  • Store metadata validation: ensure store listing assets and metadata meet platform requirements and are ready for submission.

Quick Start

Open Claude Code and trigger the release-preflight skill in your Flutter project to run all checks.

Frequently Asked Questions about release-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Flutter release readiness before submitting to app stores?

You validate Flutter release readiness by checking pubspec and platform-specific version numbers, build configurations, signing certificates, and store metadata. Running preflight checks enforces deterministic validation across iOS and Android workflows to prevent release blockers.

What does a Flutter preflight check verify in pubspec and signing configurations?

A Flutter preflight check verifies that pubspec version and build numbers are unique and incremented. It also validates iOS provisioning profiles, Android signing certificates, and Fastlane configs to ensure CI environments are ready for release.

Can I run Flutter preflight checks in both local CI and manual handoff workflows?

Yes, you can run Flutter preflight checks in local CI pipelines and manual handoff workflows. The process enforces consistent readiness across environments by reading project config files and reporting blockers related to versioning, signing, and metadata.

How do I ensure iOS and Android store metadata meets platform requirements before release?

You ensure store metadata meets requirements by validating store listing assets and metadata against platform specifications before submission. This readiness check prevents app store rejections by catching missing or non-compliant assets early in the release workflow.

What are common Flutter release blockers related to versioning and signing?

Common Flutter release blockers include duplicate or unchanged pubspec version numbers, incorrect build number increments, invalid iOS provisioning profiles, and missing Android signing certificates. Preflight validation identifies these issues deterministically before release.