ci-cd_skill

This skill helps you create and optimize Flutter/Dart CI/CD pipelines for fast feedback, stable releases, and deterministic builds.

Shell

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yelmuratoff/agent_sync --skill ci-cd

SKILL.md1.6 KB

Overview

This skill helps define and improve CI/CD workflows for Flutter and Dart repositories with a focus on fast feedback and safe delivery. It codifies best practices for triggers, deterministic jobs, caching, and release gating to reduce pipeline duration and flaky failures. The guidance targets maintainable pipelines that protect production while enabling quick iteration.

How this skill works

The skill inspects repository CI definitions and recommends changes to triggers, job ordering, caching, and version pinning. It identifies non-deterministic or shared-state jobs, suggests splitting fragile tests into separate integration flows, and proposes required checks and deployment gates. It also provides optimization tactics like dependency caching, job parallelization, and incremental test scopes.

When to use it

Creating or updating CI workflows for Flutter/Dart projects
Reducing pipeline duration, test flakiness, or CI cost
Introducing or refining release gating for production deployments
Standardizing required checks and developer fast-feedback loops
Preparing for a major release or migration of tooling/sdk versions

Best practices

Trigger CI on pull requests and pushes to main; keep required checks minimal but effective
Pin SDK and tool versions in CI and avoid shared mutable state between jobs
Run format and static analysis first, then unit/widget tests, then heavy build/signing jobs
Cache pub dependencies and reusable artifacts; parallelize independent jobs where possible
Fail fast on unstable or network-fragile tests and move them to dedicated integration flows
Protect production delivery with explicit approvals, protected jobs, feature flags, or staged rollouts

Example use cases

Convert a monolithic CI workflow into staged jobs to surface lint/test failures faster
Add dependency caching and test sharding to cut CI duration for a multi-package repo
Define required status checks and branch protection for a mobile release team
Isolate flaky integration tests into nightly pipelines and keep PR feedback quick
Introduce a protected release job with manual approval and staged rollout flags

FAQ

Move flaky or network-dependent tests out of PR-required flows into nightly or gated integration pipelines. Fail fast on core regressions in PRs and track flaky tests to prioritize fixes.

What should be required checks before merging?

Keep required checks focused: formatting, static analysis, and core unit/widget tests that prevent regressions. Add broader integration or platform-specific builds as optional or gated jobs.