Setup ci

Skill adriannoes/awesome-agentic-ai/cursor-claude-codex/skills/igoruehara-spec-driven/skills/setup-ci

329 agent skills (Cursor, Claude Code & Codex), 5,380 OpenClaw skills, 201 ML notebooks, 7 textbooks, 52 research papers, 17 industry reports for PMs, Designers & Developers.

Install

npx -y skills add adriannoes/awesome-agentic-ai --skill setup-ci

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

What its author says it does

Copied from the file, not written here

Use to create or adjust the CI/CD pipeline that materializes the SDD gates — lint, static analysis (type-check/complexity/SAST), tests (unit/integration/acceptance) and coverage from docs/engineering/TESTING.md, with coverage and static analysis published as artifacts, plus the "PR fails without an approved spec" rule. Detects GitHub Actions / GitLab CI / other. Generates the file only with approval. Trigger with /setup-ci.

SKILL.md

2.5 KB, as published. Nobody here has run it

Translation note: Originally authored in Portuguese (pt-BR) by Igor Uehara (igoruehara/spec-driven, MIT). Translated to English by this hub to keep the repository language consistent. Original content unchanged in meaning; see the upstream repo for the pt-BR source.

Skill: CI/CD setup (SDD gates in the pipeline)

Materializes the SDD gates in the automated pipeline — this is where "a document the team tries to follow" becomes "rules the system enforces". Idempotent: re-running adjusts the existing pipeline.

Discover the target

Detect the provider (GitHub Actions / GitLab CI / Bitbucket / other) from the repo and from integrations.md.
Read docs/engineering/TESTING.md (gate commands) and the quality gate from CLAUDE.md (minimum coverage).

Propose the pipeline (confirm before generating)

Stages in order; failing blocks the merge:

Lint/format → 2. Static analysis (type-check + complexity + SAST) → 3. Unit → 4. Integration → 5. Acceptance (one per AC-N) → 6. Coverage (min. from CLAUDE.md).
SDD rule: a PR that changes code without an approved spec in specs/ → fails (a job that checks the presence/status of the spec corresponding to the change).

Traceable evidence: publish coverage and static analysis as artifacts of the run (and, if the provider allows, as a check/comment on the PR). The quality result gets attached to the change and feeds the trend for /metricas.

Generate

The pipeline file (.github/workflows/*.yml / .gitlab-ci.yml) using the commands from docs/engineering/TESTING.md — do not invent commands; reuse the ones there.
⚠️ No secrets in the file — use the provider's secrets. Confirm before writing.
Record the pipeline choice as an ADR if it is structural; reference it in docs/engineering/agentic-layer.md.

Next step

Pair with /revisar-pr (human/agent gate). Together they cover review + automation: CI enforces tests/coverage/spec; /revisar-pr enforces process conformance on the PR/MR.