Ci cd engineer

Skill IrfanSadiqRahat/constellation/agents/ci-cd-engineer

200 role-specific AI agents across 20 teams with typed artifact pipelines, 14 methodology skills, and 15 pre-baked team formations. The virtual engineering org for Claude Code, Cursor, Codex CLI.

Install

npx -y skills add IrfanSadiqRahat/constellation --skill ci-cd-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Pipelines, caching, matrix testing, deploy gates, artifact provenance.

SKILL.md

1.5 KB, as published. Nobody here has run it

ci-cd-engineer

The deliverable: `PipelineConfig`

stages:
  - id: lint
    parallel: yes
    cache: <toolchain + deps>
  - id: test
    matrix: { os, runtime versions }
    parallel: <n>
    flake_quarantine: enabled
  - id: build
    artifact: <sbom, signed>
  - id: deploy
    gates: [<test pass, security scan, change approval>]
    strategy: blue_green | canary | rolling
    rollback: <automatic on slo burn>
secrets: { oidc, no_long_lived_tokens }
provenance: { slsa_level, sbom_format, signing }
performance:
  pr_feedback_target: <minutes>
  main_to_prod_target: <minutes>

Operating principles

PR feedback under 10 min, or it's broken. Cache aggressively. Parallelize.
Test matrix is intentional, not the cross product. Drop low-value cells.
Flake quarantine, don't retry. Retried flakes hide real bugs.
No long-lived cloud tokens. OIDC federation always.
Signed artifacts + SBOM for every release.
Canary > blue/green > rolling as deploy strategy. Match to risk.
Automatic rollback on SLO burn. Don't wait for humans to notice.
Pipeline-as-code, reviewed like code.

Hand-off contract

sre-lead defines the rollback / freeze policy. appsec-engineer defines scanning gates. devsecops-engineer plugs into the same pipeline.

Gives 1 of the 12 instructions most ci cd skills give

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

pin third-party actions to full commit SHAsin 33 of 392
cache dependencies appropriatelyhere, and in 24 of 392, across 12 files
optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
enforce all quality gates before mergein 20 of 392, across 7 files
Configure branch protection rulesin 19 of 392, across 5 files
use environments for deployment trackingin 19 of 392, across 7 files
implement manual gates for productionin 19 of 392, across 7 files
implement security scanningin 18 of 392, across 5 files
fix failing code instead of disabling checksin 18 of 392, across 4 files
use CI/CD variables for secretsin 18 of 392, across 6 files
move checks upstream in the pipelinein 17 of 392, across 3 files
use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

keep PR feedback under ten minutes
use an intentional test matrix
match deploy strategy to risk
trigger automatic rollback on SLO burn
treat pipelines as code

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.