envy-7z/mobile-ci-release-flow
skills/mobile-ci-release-flow/SKILL.md
Android and Flutter CI/release readiness workflow for branch validation, failure triage, QA checklist creation, and release-note risk review. Use when preparing mobile PRs for merge, fixing broken CI, validating a release candidate, or deciding go/no-go for internal or store release.
development
Updated Apr 5, 2026
$ install --global
skillsauthnpx skillsauth add envy-7z/mobile-agent-skillpack mobile-ci-release-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 2:00 AM8.8s4 files scanned
SKILL.md
- name:
- mobile-ci-release-flow
- description:
- Android and Flutter CI/release readiness workflow for branch validation, failure triage, QA checklist creation, and release-note risk review. Use when preparing mobile PRs for merge, fixing broken CI, validating a release candidate, or deciding go/no-go for internal or store release.
Mobile CI Release Flow
Overview
Run a repeatable go/no-go workflow for Android and Flutter branches. Detect project stack, execute targeted verification, triage failures by root cause, and publish a release-readiness summary.
Workflow
- Detect stack and pipeline
- Run
scripts/ci_release_snapshot.sh <repo_root>first. - Read detected CI files, Android modules, Flutter apps, and version markers before selecting commands.
- Execute the minimal verification matrix
- For Android projects with
gradlew, run from repo root:./gradlew test lint assembleDebug. - For Flutter projects with
pubspec.yaml, run:flutter pub get,flutter analyze,flutter test. - Add project-specific CI commands only when they already exist in pipeline config.
- Triage failures with root-cause priority
- Classify failures as compile, test, lint, configuration/signing, dependency resolution, or infrastructure flake.
- Fix the earliest causal failure first; avoid fixing downstream noise first.
- Prefer the smallest safe patch; avoid architecture refactors during CI stabilization.
- Evaluate release readiness
- Confirm version markers are updated where required (
versionCode/versionName,pubspec.yamlversion). - Confirm release notes or
CHANGELOG.mdinclude user-visible changes and known risks. - Confirm blocker-level crash risks are addressed for primary user flows.
- Produce decision output
- Return one of:
GO,GO WITH RISKS,NO-GO. - Include blocker list, warning list, and explicit next actions.
Output Format
Use this exact section structure in the final response:
# CI + Release Readiness
## Decision
GO | GO WITH RISKS | NO-GO
## Blockers
- ...
## Warnings
- ...
## Evidence
- Commands executed:
- Key failing/passing targets:
- CI files reviewed:
## Release Notes Draft
- User-visible changes:
- Risk notes:
## Next Actions
1. ...
2. ...
Guardrails
- Preserve existing repository conventions and CI style.
- Do not remove tests to make CI green.
- Do not change signing/release keys unless explicitly requested.
- Flag flaky tests separately from deterministic failures.
References
- Use
references/release-checklists.mdfor Android/Flutter release QA criteria.
Related Skills
envy-7z/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec or requirements for a multi-step task, before touching code
SKILL.mdUpdated Apr 5, 2026
envy-7z/verification-before-completion
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
SKILL.mdUpdated Apr 5, 2026
envy-7z/using-git-worktrees
tools
VerifiedTrustedCommunity
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
SKILL.mdUpdated Apr 5, 2026
envy-7z/thinkies
testing
VerifiedTrustedCommunity
Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions.
SKILL.mdUpdated Apr 5, 2026