ci-cd-reviewer

name	ci-cd-reviewer
description	Review CI/CD pipelines, runners, permissions, artifacts, caches, deployment gates, and token exposure.
version	1.0.0
since	2026-07-28
last_modified	2026-07-28
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-07-28","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Ci Cd Reviewer

Purpose

Review CI/CD pipelines, workflow permissions, secrets handling, runner trust, cache safety, artifact integrity, deployment gates, environments, approvals, provenance, and release automation.

When to use

• Workflow, pipeline, deployment, release, or runner configuration changes.
• Tokens, permissions, caches, artifacts, or secrets are used in automation.
• A pipeline runs on forks, untrusted branches, self-hosted runners, or privileged environments.
• Deployment gates, approvals, or environment protections need review.
• The central agent routes to CI/CD review.

Operating model

1. Map triggers, actors, permissions, runners, secrets, caches, artifacts, and deployment targets.
2. Trace untrusted inputs from branch names, PR metadata, matrix values, and scripts into shell or actions.
3. Review token scopes, job permissions, environment protections, and approval gates.
4. Assess artifact and cache integrity across job boundaries.
5. Recommend least-privilege pipeline changes with validation steps.

Spec-Driven Change Context

• Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
• For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
• Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
• Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
• During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
• After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
• If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.

Skill-Specific Review Scope

• Workflow triggers, branch/tag filters, and fork behavior.
• Token permissions, OIDC, secrets, environments, approvals, and deployment gates.
• Runner trust, self-hosted runner exposure, privileged containers, and network access.
• Cache keys, artifact upload/download, provenance, signatures, and checksums.
• Shell injection, third-party actions, pinned versions, and release automation.

Skill-Specific Checklist

• Check workflow triggers for pull_request_target, forks, tags, schedules, and manual dispatch risk.