Diagnose and fix failing CircleCI builds. Use when the user asks to investigate CI failures, fix a broken build, or debug CircleCI pipeline issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/circleci-failing-builds:circleci-failing-buildsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Always use `cci-failed-logs` first.** It handles token auth, org/repo detection, pipeline discovery, and log fetching in a single non-interactive call.
Always use cci-failed-logs first. It handles token auth, org/repo detection, pipeline discovery, and log fetching in a single non-interactive call.
CCI=~/Development/dotfiles/bin/cci-failed-logs
# Latest failures on current branch (most common)
$CCI
# Specific branch
$CCI --branch main
# Specific job number (from a CircleCI URL — fastest, skips discovery)
$CCI --job 333
# Just list which jobs failed, no logs
$CCI --summary
# Limit log output per step (default: 200 lines)
$CCI --max-lines 50
If the user provides a CircleCI URL, extract the job number (last path segment) and use --job:
https://app.circleci.com/pipelines/github/ORG/REPO/PIPELINE_NUM/workflows/WORKFLOW_ID/jobs/JOB_NUMBER
^^^^^^^^^^
$CCI --job JOB_NUMBER
The script outputs structured, machine-readable text:
project: Org/Repo
branch: feature-branch
pipeline: uuid
failed_jobs: 2
=== JOB: test-suite (#333) ===
--- STEP: Run tests [failed] ---
<log lines, truncated to --max-lines>
--- END STEP ---
=== END JOB ===
$CCI or $CCI --job NUMBERbundle install / npm install / equivalent..circleci/config.yml syntax with circleci config validate if the CLI is installed.Only use raw API calls if the script fails or you need data it doesn't provide.
TOKEN=$(grep 'token:' ~/.circleci/cli.yml | awk '{print $2}')
# v1.1 API (more reliable with personal tokens)
# Get step-level detail for a specific job
curl -sf -H "Circle-Token: $TOKEN" \
"https://circleci.com/api/v1.1/project/github/ORG/REPO/JOB_NUMBER" \
| jq '[.steps[] | select(.actions[0].status == "failed") | {name: .name, status: .actions[0].status, output_url: .actions[0].output_url}]'
# Fetch log output from a failed step's output_url
curl -s "OUTPUT_URL" | gunzip 2>/dev/null | jq -r '.[].message'
# List recent failed builds for a branch
curl -sf -H "Circle-Token: $TOKEN" \
"https://circleci.com/api/v1.1/project/github/ORG/REPO/tree/BRANCH?limit=10&filter=failed"
IMPORTANT: The v2 API often returns 404 with personal API tokens (CCIPAT_...). Always prefer v1.1. Note v1.1 uses github (not gh) as the VCS prefix.
.circleci/config.yml in ways that skip tests, disable checks, or weaken the pipeline.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub mikesilvis/ai-skills --plugin circleci-failing-builds