A troubleshooting command for diagnosing and fixing failed CI pipeline runs. CI, or continuous integration, automatically checks code when changes are submitted.

Use it with a GitHub or GitLab run URL, a log file, or discovered project logs, and focus on areas such as tests, linting, or Docker.

It helps turn confusing build logs and pipeline failures into a diagnosis and proposed fix, with approval before changes are applied.

ci-fix — Command for Claude Code by dykyi-roman: A troubleshooting command for diagnosing and fixing failed 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.

agentmods

npx agentmods add commands/dykyi-roman/awesome-claude-code/ci-fix

Clone the repo

git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code

Made for: Claude Code.

Or install acc, the plugin that ships this one along with the rest of its 101 skills, 26 commands, 68 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/ci-fix.svg)](https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/ci-fix)

Your own site

<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/ci-fix"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/ci-fix.svg" alt="Measured on agentmods" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,836 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.01836
Opus 5	$0.00003	$0.00918
Sonnet 5	$0.00001	$0.00367
Haiku 4.5	$0.00001	$0.00184

Measured 2d ago against content hash f78920907d39, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

ci-fix 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 2d 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.

commands/ci-fix.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI Fix Command

You are executing the /acc:ci-fix command. Your task is to diagnose CI pipeline issues and apply fixes with user approval.

Input Received

User Input: $ARGUMENTS

Meta-Instructions: Parse any text after -- as meta-instructions:

-- dry-run — Show diagnosis and fix without applying or asking
-- auto-apply — Apply fix without asking (for CI/scripts)
-- verbose — Include detailed diagnosis output
-- skip-validation — Don't run local syntax checks
-- focus on <area> — Prioritize specific area (tests, lint, docker)

Execution Flow

Step 1: Parse Input

Determine the input type:

Pipeline URL (contains github.com/ or gitlab.com/)
- Extract repository and run ID
- Use gh CLI to fetch logs if GitHub
- Parse URL for context
Log File Reference (file path or starts with @)
- Read the log file
- Extract error messages and context
Auto-discover CI Logs (when -- scan-logs is specified or no log file provided with -- scan-logs)
- Use acc:discover-project-logs skill via ci-debugger to find CI build logs:
  - build/logs/*.log, build/logs/*.xml
  - build/reports/*.xml
  - PHPUnit/PHPStan output files
- If no logs found, use AskUserQuestion:
```
Question: "CI log files not found automatically. Where are your CI logs?"
Options:
  - "build/logs/" (PHPUnit/PHPStan output)
  - "build/reports/" (CI reports)
  - "Paste pipeline URL" (GitHub Actions / GitLab CI)
```
Text Description
- Search codebase for CI configuration
- Use description to guide diagnosis

Step 2: Locate CI Configuration

Find CI configuration files:

Task → Explore agent

Find CI configuration files:
- .github/workflows/*.yml (GitHub Actions)
- .gitlab-ci.yml (GitLab CI)
- phpstan.neon, psalm.xml (static analysis)
- phpunit.xml (testing)
- Dockerfile, docker-compose.yml (Docker)

Step 3: Diagnose Issue

Invoke acc:ci-debugger agent to diagnose:

Read the full file on GitHub · 287 lines

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.

2d ago First seen · 287 lines · 7 tokens per session scan A f78920907d39

Subscribe to this mod's changes

ci-fix is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 7 tokens to every session and 1,836 once invoked, about $0.0000 per session on Opus 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-09-03.

CI and CD Containers Debugging DevOps and cloud

ci-fix

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CI Fix Command

Input Received

Execution Flow

Step 1: Parse Input

Step 2: Locate CI Configuration

Step 3: Diagnose Issue

What this file has done since we first saw it

Other commands, from other repositories

sparc-devops

docker-build-push

ops-k8s

deploy-check

arckit.devops

sparc-devops