Skip to content
Skills Library
DevOps & cloud · Analysis

ci

/ci

CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.

Licence
MIT
Last repository change
03.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.

Arguments

/ci [analyze|fix|run]
Original author description

CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.

How it works

  1. Trigger Conditions
  2. Feature Details
  3. Execution Steps
  4. Sub-agent Integration
  5. For VibeCoder
Original SKILL.md headings · 187 lines, 688 words
SKILL.md preview
---
name: ci
description: "CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup."
description-en: "CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup."
allowed-tools: ["Read", "Grep", "Bash", "Task", "Monitor"]
user-invocable: true
context: fork
argument-hint: "[analyze|fix|run]"
---

# CI/CD Skills

A set of skills for resolving CI/CD pipeline issues.

---

## Trigger Conditions

- "CI failed", "GitHub Actions failure"
- "Build error", "Tests won't pass"
- "Fix the pipeline"

---

## Feature Details

| Feature | Details | Trigger |
|---------|---------|---------|
| **Failure Analysis** | See [references/analyzing-failures.md](${CLAUDE_SKILL_DIR}/references/analyzing-failures.md) | "Read the log", "Investigate the cause" |
| **Test Fixing** | See [references/fixing-tests.md](${CLAUDE_SKILL_DIR}/references/fixing-tests.md) | "Fix the test", "Suggest a fix" |

---

## Execution Steps

1. **Test vs. Implementation determination** (Step 0)
2. Classify user intent (analyze or fix)
3. Assess complexity (see below)
4. Read the appropriate reference file from "Feature Details" above, or launch the ci-cd-fixer sub-agent
5. Review results and re-run if necessary

### Step 0: Test vs. Implementation Determination (Quality Gate)

When a CI failure occurs, first triage the cause:

```
CI failure reported
    ↓
┌─────────────────────────────────────────┐
│       Test vs. Implementation           │
├─────────────────────────────────────────┤
│  Analyze the cause:                     │
│  ├── Implementation is wrong → Fix impl │
│  ├── Test is outdated → Confirm w/ user │
│  └── Environment issue → Fix env        │
└─────────────────────────────────────────┘
```

#### Prohibited Actions (Anti-tampering)

```markdown
⚠️ Prohibited actions when CI fails

The following "solutions" are prohibited:

| Prohibited | Example | Correct approach |
|------------|---------|------------------|
| Skipping tests | `it.skip(...)` | Fix the implementation |
| Removing assertions | Delete `expect()` | Verify expected values |
| Bypassing CI checks | `continue-on-error` | Fix the root cause |
| Relaxing lint rules | `eslint-disable` | Fix the code |
```

#### Decision Flow

```markdown
🔴 CI is failing

**A decision is needed**:

1. **Implementation is wrong** → Fix the implementation ✅
2. **Test expected value is outdated** → Ask user for confirmation
3. **Environment issue** → Fix the environment configuration

⚠️ Tampering with tests (skipping, removing assertions) is prohibited

Which applies here?
```

#### When Approval Is Needed

If changes to tests/configuration are unavoidable:

```markdown
## 🚨 Approval Request for Test/Config Change

### Reason
[Why this change is necessary]

### Change Content
[Diff]

### Alternatives Considered
- [ ] Confirmed that fixing the implementation cannot resolve this

Waiting for explicit user approval
```

### Using Extended Git Log Flags (CC 2.1.49+)

Use structured logs to identify the commit that caused the CI failure.

#### Identifying the Culprit Commit

```bash
# Analyze commits with structured format
git log --format="%h|%s|%an|%ad" --date=short -10

# Analyze chronologically with topological order
git log --topo-order --oneline -20

# Link changed files to causes
git log --raw --oneline -5
```

#### Key Use Cases

| Use | Flag | Effect |
|-----|------|--------|
| **Identify failure cause** | `--format="%h|%s"` | Structured commit list |
| **Chronological tracking** | `--topo-order` | Track considering merge order |
| **Understand change impact** | `--raw` | Detailed file change display |
| **Exclude-merge analysis** | `--cherry-pick --no-merges` | Extract only real commits |

#### Sample Output

```markdown
🔍 CI Failure Cause Analysis

Recent commits (structured):
| Hash | Subject | Author | Date |
|------|---------|--------|------|
| a1b2c3d | feat: update API | Alice | 2026-02-04 |
| e4f5g6h | test: add tests | Bob | 2026-02-03 |

Changed files (--raw):
├── src/api/endpoint.ts (Modified) ← type error here
├── tests/api.test.ts (Modified)
└── package.json (Modified)

→ Commit a1b2c3d is likely the cause
  Type error: src/api/endpoint.ts:42
```

## Sub-agent Integration

Launch ci-cd-fixer via the Task tool when the following conditions are met:

- Fix → re-run → fail loop has occurred **2 or more times**
- Or the error spans multiple files in a complex case

**Launch pattern:**

```
Task tool:
  subagent_type="ci-cd-fixer"
  prompt="Please diagnose and fix the CI failure. Error log: {error_log}"
```

ci-cd-fixer operates with safety first (default dry-run mode).
See `agents/ci-cd-fixer.md` for details.

---

## For VibeCoder

```markdown
🔧 How to talk about broken CI

1. **"CI failed" / "It went red"**
   - Automated tests are failing

2. **"Why is it failing?"**
   - Investigate the cause

3. **"Fix it"**
   - Attempt automatic repair

💡 Important: Fixes that "cheat" tests are prohibited
   - ❌ Deleting or skipping tests
   - ✅ Properly fixing the code

If you think "the test seems wrong",
confirm first before deciding on a course of action
```
Files in this package (3)
  • SKILL.md 6 KB
  • references/analyzing-failures.md 4 KB
  • references/fixing-tests.md 4 KB

Versions

RepositoryScoreLicence
This page · maxwell2732/claudecode-research-harness-workflow100MIT
A7-studio/jobmigo100MIT
gagarin-cloud/plugin100MIT
andriiklymiuk/corgi100MIT
kamoca-labs/docker100MIT
pawangai/pawang-agents100MIT
agentic-dev3o/devx-plugins100MIT
chachamaru127/claude-code-harness100MIT
onsi/ginkgo100MIT

Database snapshot: 13.11.2026 · package version d000c4fa1cdf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ci-debugging
    Diagnose and fix CI/CD pipeline failures: GitHub Actions errors, build failures, test timeouts, TLS/auth issues, platform-specific failures, dependency resolution problems, and deployment errors. Use when CI checks fail, builds break, tests timeout, or pipeline errors need…
  • 100gitlab-cicd-debug
    Debug GitLab CI/CD pipeline failures including vault auth, docker builds, K8s deployments, and job errors. Use when: (1) Pipeline jobs fail, (2) Vault JWT auth issues, (3) Docker build/push errors, (4) K8s deployment failures, (5) "permission denied" or "unauthorized" errors,…
  • 90fix-issues
    Use when fixing software issues in a repository, including bug reports, failing tests, CI failures, compile errors, runtime errors, regressions, dependency problems, and requests such as "fix this issue", "resolve this bug", "make tests pass", or "address the failure". Guides…
  • 100pipeline-test-triage
    Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug",…
  • 100diagnose-ci-failures
    Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
  • 100relay-pipeline
    Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.