setup-ci

setup-ci is a skill for Claude Code from igoruehara/spec-driven. It costs 112 tokens per session (627 once invoked), scanned A, original, MIT.

A setup process for turning a project's testing and quality rules into an automated CI/CD pipeline. CI/CD means that a service automatically checks code changes and can block merging when required checks fail.

In plain words
What is it for?
Creating or adjusting GitHub Actions, GitLab CI, or similar pipelines for formatting, type checks, security analysis, unit tests, integration tests, acceptance tests, coverage, and specification checks.
Why use it?
It replaces a document that people must remember with checks the repository enforces. It also keeps test coverage and static-analysis results attached to each pipeline run.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

Good fit Creating or adjusting GitHub Actions, GitLab CI, or similar pipelines for formatting, type checks, security analysis, unit tests, integration tests, acceptance tests, coverage, and specification checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/igoruehara/spec-driven/setup-ci
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add igoruehara/spec-driven --skill setup-ci
Clone the repo
git clone --depth 1 https://github.com/igoruehara/spec-driven

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for setup-ci

README.md
[![agentmods](https://agentmods.dev/badge/skills/igoruehara/spec-driven/setup-ci/github.svg)](https://agentmods.dev/skills/igoruehara/spec-driven/setup-ci)
Your own site
<a href="https://agentmods.dev/skills/igoruehara/spec-driven/setup-ci"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/setup-ci/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for setup-ci

Your own site · 80×15
<a href="https://agentmods.dev/skills/igoruehara/spec-driven/setup-ci"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/setup-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00112 $0.00627
Opus 5.5 $0.00045 $0.00251
Sonnet 5.5 $0.00022 $0.00125
Haiku 4.5 $0.00011 $0.00063

Measured 1mo ago against content hash b457d50286e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-ci scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

template/.claude/skills/setup-ci/SKILL.md · 35 lines

What it actually says

Skill: Setup de CI/CD (gates SDD na pipeline)

Materializa os gates SDD na esteira automática — é onde "documento que o time tenta seguir" vira "regra que o sistema garante". Idempotente: re-rodar ajusta a pipeline existente.

Descubra o alvo

  • Detecte o provedor (GitHub Actions / GitLab CI / Bitbucket / outro) pelo repo e por integrations.md.
  • Leia docs/engineering/TESTING.md (comandos de gate) e o quality gate do CLAUDE.md (cobertura mínima).

Proponha a pipeline (confirme antes de gerar)

Estágios em ordem; falhar bloqueia o merge:

  1. Lint/format → 2. Análise estática (type-check + complexidade + SAST) → 3. Unidade → 4. Integração → 5. Aceite (um por AC-N) → 6. Cobertura (mín. do CLAUDE.md).
  2. Regra SDD: PR que altera código sem spec aprovada em specs/ → falha (job que checa a presença/status da spec correspondente à mudança).

Evidência rastreável: publique cobertura e análise estática como artefatos do run (e, se o provedor permitir, como check/comentário no PR). O resultado de qualidade fica anexado à mudança e alimenta a tendência do /metricas.

Gere

  • O arquivo da pipeline (.github/workflows/*.yml / .gitlab-ci.yml) usando os comandos de docs/engineering/TESTING.md — não invente comandos; reuse os de lá.
  • ⚠️ Sem segredos no arquivo — use os secrets do provedor. Confirme antes de escrever.
  • Registre a escolha de pipeline como ADR se for estrutural; aponte em docs/engineering/agentic-layer.md.

Próximo passo

Combine com /revisar-pr (gate humano/agente). Juntos cobrem review + automação: a CI garante os testes/cobertura/spec; o /revisar-pr garante a conformidade de processo no PR/MR.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 35 lines · 112 tokens per session scan A b457d50286e9

Subscribe to this mod's changes

setup-ci is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 627 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens

quality-scan

Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.

diegosouzapw/OmniRoute · 45 tokens

e2e-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

thedaviddias/Front-End-Checklist · 38 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens

test-setup

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

Donchitos/Claude-Code-Game-Studios · 32 tokens