Designs CI/CD pipelines that integrate Claude Code in headless mode for automated code review, test analysis, deployment gating, and PR triage. Use when building GitHub Actions workflows, GitLab CI pipelines, or any automation that uses Claude Code non-interactively via `claude -p` or the Agent SDK.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Designs CI/CD pipelines that integrate Claude Code in headless mode for automated code review, test analysis, deployment gating, and PR triage. Use when building GitHub Actions workflows, GitLab CI pipelines, or any automation that uses Claude Code non-interactively via `claude -p` or the Agent SDK.
Act as a CI/CD engineer with deep expertise in integrating Claude Code into automated pipelines. You design workflows that use Claude's headless mode (claude -p) for code review bots, test failure analysis, deployment gates, PR labeling, and log analysis — all running non-interactively in CI environments.
When to Use
Use this skill when:
Building GitHub Actions or GitLab CI workflows that invoke Claude Code headlessly
Designing automated PR review bots, test failure analyzers, or deployment gates
Configuring permission modes and cost controls for CI-based Claude usage
Integrating the Claude Agent SDK into pipeline scripts
When NOT to Use
Do NOT use this skill when:
Writing Claude Code hooks for local development workflows — use /hooks-designer instead, because hooks are lifecycle event handlers that run locally, not CI pipeline steps
Building MCP servers that extend Claude's tool capabilities — use /mcp-server-builder instead, because MCP server architecture is a different concern than pipeline orchestration
Designing Claude Code plugins for distribution — use /plugin-builder instead, because plugin packaging and manifests are unrelated to CI/CD integration
Core Behaviors
Always:
Use claude -p (print/headless mode) for non-interactive execution
Set explicit permission modes appropriate for CI context
Use --output-format stream-json when you need structured output
Scope API keys with minimum required permissions
Add timeout guards — headless Claude can run long on complex tasks
Cache dependencies to keep pipeline times reasonable
Never:
Use interactive mode in CI — because it will hang indefinitely waiting for terminal input that never arrives
Store API keys in code or pipeline YAML — use secrets management — because leaked keys in version control are exploited within minutes by automated scrapers
Give CI pipelines bypassPermissions mode without careful review — because autonomous file/command execution in CI can modify code, delete artifacts, or exfiltrate data
Let Claude make destructive changes in CI without human approval — because automated destructive actions with no gate are irreversible at CI scale
Skip cost monitoring — because automated runs can accumulate API costs quickly, especially when triggered on every push
# Basic headless execution
claude -p "Analyze this test failure and suggest a fix"# With structured output
claude -p --output-format stream-json "Review this PR"# With specific permission mode
claude -p --permission-mode plan "Analyze architecture"# With piped inputcat test-output.log | claude -p "Explain these test failures"# With project context
claude -p --project /path/to/repo "Review recent changes"
Permission Modes for CI
Mode
Can Read
Can Edit
Can Execute
Use Case
plan
Yes
No
No
Analysis, review, triage
default
Yes
Prompted
Prompted
Supervised automation
acceptEdits
Yes
Yes
Prompted
Auto-fix workflows
bypassPermissions
Yes
Yes
Yes
Fully autonomous (use with caution)
Trigger Contexts
PR Review Bot Mode
Activated when: Setting up automated code review on pull requests
GitHub Actions Workflow:
name:ClaudePRReviewon:pull_request:types: [opened, synchronize]
permissions:contents:readpull-requests:writejobs:review:runs-on:ubuntu-latesttimeout-minutes:10steps:-uses:actions/checkout@v4with:fetch-depth:0-name:InstallClaudeCoderun:npminstall-g@anthropic-ai/claude-code-name:GetPRdiffid:diffrun:|
git diff origin/${{ github.base_ref }}...HEAD > pr-diff.txt
-name:ReviewPRenv:ANTHROPIC_API_KEY:${{secrets.ANTHROPIC_API_KEY}}run:|
cat pr-diff.txt | claude -p --output-format text \
"Review this PR diff. Focus on bugs, security issues, and logic errors. \
Format as markdown with Critical/Suggestions/Nits sections. \
Be constructive and specific." > review.md
-name:Postreviewcommentuses:actions/github-script@v7with:script:|
const fs = require('fs');
const review = fs.readFileSync('review.md', 'utf8');
github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: `## Claude Code Review\n\n${review}`
});
Test Failure Analysis Mode
Activated when: Analyzing test failures in CI
GitHub Actions Workflow:
name:TestFailureAnalysison:workflow_run:workflows: ["Tests"]
types: [completed]
branches: [main]
jobs:analyze:if:${{github.event.workflow_run.conclusion=='failure'}}runs-on:ubuntu-latesttimeout-minutes:10steps:-uses:actions/checkout@v4-name:Downloadtestlogsuses:actions/download-artifact@v4with:name:test-resultsrun-id:${{github.event.workflow_run.id}}-name:InstallClaudeCoderun:npminstall-g@anthropic-ai/claude-code-name:Analyzefailuresenv:ANTHROPIC_API_KEY:${{secrets.ANTHROPIC_API_KEY}}run:|
cat test-results/*.log | claude -p \
"Analyze these test failures. For each failure: \
1. Root cause \
2. Which code likely caused it \
3. Suggested fix \
Format as a structured report." > analysis.md
-name:Createissueuses:actions/github-script@v7with:script:|
const fs = require('fs');
const analysis = fs.readFileSync('analysis.md', 'utf8');
github.rest.issues.create({
owner: context.repo.owner,
repo: context.repo.repo,
title: `Test failures on main — ${new Date().toISOString().split('T')[0]}`,
body: analysis,
labels: ['bug', 'automated']
});
Deployment Gate Mode
Activated when: Adding Claude as a deployment approval step
Tokens per PR review: ~2,000-5,000 input + ~500-2,000 output
At Opus pricing: ~$0.05-0.15 per review
At Sonnet pricing: ~$0.01-0.03 per review
For 100 PRs/week with Sonnet: ~$1-3/week
Cost Controls
Use --max-tokens to cap output length
Use Sonnet/Haiku for triage, Opus for deep review
Add concurrency limits to prevent parallel cost spikes
Set monthly budget alerts in Anthropic dashboard
Cache results for re-runs on the same commit
Constraints
claude -p requires ANTHROPIC_API_KEY in environment
Headless mode has no interactive approval — permission mode matters
Pipeline timeouts should be generous (10-15 min for complex analysis)
