github-actions
Orchestrate CI/CD pipelines with GitHub Actions for Flutter apps. Use when setting up quality gates, automated builds, semantic versioning, code signing, or deployment workflows.
What this skill does
# GitHub Actions Pipeline - Use GitHub Actions as the primary CI/CD platform - Trigger on `push` to `main` and on all Pull Requests - Pipeline MUST include these stages in order: ## Stage 1: Quality Gate ```yaml - name: Analyze run: flutter analyze --fatal-infos --fatal-warnings - name: Format Check run: dart format --set-exit-if-changed . - name: Run Tests run: flutter test --coverage ``` - Zero warnings policy — `--fatal-infos` ensures no info-level issues pass - Format check MUST use `--set-exit-if-changed` to enforce consistent formatting ## Stage 2: Build ```yaml - name: Build APK run: flutter build apk --flavor prod --dart-define-from-file=config/prod.json --release - name: Build IPA run: flutter build ipa --flavor prod --dart-define-from-file=config/prod.json --release --export-options-plist=ios/ExportOptions.plist ``` - Always build with `--flavor prod` and `--dart-define-from-file=config/prod.json` - Use a single `main.dart` — do NOT pass `-t lib/main_prod.dart` ## Stage 3: Deploy (on main merge only) - Upload to Firebase App Distribution for internal testing - Upload to Google Play Internal Track / TestFlight for staging - Production release requires manual approval gate # Versioning Strategy - Follow Semantic Versioning: `MAJOR.MINOR.PATCH+BUILD` - Bump `PATCH` for bug fixes, `MINOR` for features, `MAJOR` for breaking changes - Set version in `pubspec.yaml`: `version: 1.2.3+45` - The `+BUILD` number MUST auto-increment in CI (use build number from CI environment) # Code Signing - Store signing keys and certificates in GitHub Secrets (never in repo) - Android: Store keystore as base64-encoded secret, decode in CI - iOS: Use App Store Connect API key for automated signing - NEVER commit `*.jks`, `*.keystore`, `*.p12`, or `*.mobileprovision` files # PR Requirements - All PRs MUST pass: analysis (0 warnings), formatting, and tests before merge - Require at least 1 code review approval - Branch protection on `main`: no direct pushes, require status checks # Release Checklist - [ ] Version bumped in `pubspec.yaml` - [ ] CHANGELOG.md updated - [ ] All tests passing on CI - [ ] Build succeeds for both Android and iOS - [ ] Tested on physical device with production flavor - [ ] Git tag created matching version (`v1.2.3`)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.