Agent skill

CI Debugging

by citypaul in citypaul/.dotfiles

Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis.

Custom licenceAuto-check: notesDevOps & Cloud

Install CI Debugging

skills CLI
$ npx skills add citypaul/.dotfiles --skill ci-debugging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install citypaul/.dotfiles ci-debugging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/citypaul/.dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/.claude/skills/ci-debugging .claude/skills/ci-debugging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ci-debugging
GitHub stars
739
Token cost
~1.5k tokens
SKILL.md length
760 words
Files
1
Skills in repo
44
Repo updated
First seen
Licence
Custom licence

At a glance

Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis.

  • Works in 3 steps: Test relies on network access… → Parallel test execution causes resource… → CI runner has less memory/CPU than local…
  • GitHub Actions workflow
  • SKILL.md covers Getting the Data, Hypothesis-First Diagnosis, Local Reproduction and Environment Delta Analysis, plus 5 more sections
  • Calls gh, node and npm

What it does

CI Debugging is an agent skill from citypaul/.dotfiles. Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis. Use when a CI pipeline, GitHub Actions workflow, or build job fails; when tests pass locally but fail in CI; when diagnosing flaky tests, timeouts, or red pipelines; or when the user says "CI is failing", "the build is broken", or "works on my machine".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD, Failing and flaky tests and Debugging. It works with GitHub Actions.

When your agent uses it

  • GitHub Actions workflow
  • Build job fails
  • Tests pass locally but fail in CI
  • Diagnosing flaky tests

Example prompts

  • “CI is failing”
  • “the build is broken”
  • “works on my machine”
  • “/ci-debugging”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Test relies on network access unavailable in CI
  2. Parallel test execution causes resource contention
  3. CI runner has less memory/CPU than local machine

What it can do on your machine

Read from SKILL.md and the folder at commit cd4028d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • node
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI Debugging loads about 1.5k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 760 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:66
    | Env vars | CI secrets/config vs local `.env` |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 760 words (~1,504 tokens).

“Every CI failure is real until proven otherwise. Never assume flakiness.”

— opening of SKILL.md by citypaul, Custom licence
name
ci-debugging

Read the full SKILL.md on GitHub

Files

Just SKILL.md in claude/.claude/skills/ci-debugging of citypaul/.dotfiles.

Open the folder on GitHubat commit cd4028d

Compare with similar skills

CI Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CI Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CI Debugging this skillcitypaul/.dotfiles739—~1.5kAutomated safety check: NotesCustom licence
CI/CD Failure Troubleshootingruby-git/ruby-git1.8k—~1.9kAutomated safety check: PassMIT
CI Workflow Guidesgl-project/sglang37k2 repos~5.5kAutomated safety check: PassApache-2.0
Debugging CI FailuresPostHog/posthog-foss721—~5.7kAutomated safety check: PassMIT
CI Failure Triage and RepairChachamaru127/claude-code-harness3.2k1 repos~1.1kAutomated safety check: NotesMIT
CI Watchdoglatitude-dev/latitude-llm4.7k—~1.6kAutomated safety check: PassMIT

Similar skills

  • Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • CI Workflow Guide

    sgl-project/sglang

    Guide to SGLang CI workflow orchestration — stage ordering, fail-fast, gating, partitioning, execution modes, and debugging CI failures.

    37k GitHub starsUsed in 2 repos~5.5k tokens
    DevOps & CloudAuto-check passed
  • Debugging CI Failures

    PostHog/posthog-foss

    Official

    Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").

    721 GitHub stars~5.7k tokensUpdated today
    Testing & QAAuto-check passed
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes
  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from citypaul/.dotfiles

All 44 skills in this repo
  • Find Skills

    citypaul/.dotfiles

    Discover and, with authorization, install agent skills from the open skills ecosystem.

    739 GitHub stars~2.5k tokensUpdated 5 days ago
    Auto-check passed
  • Render Code Shape

    citypaul/.dotfiles

    Render the shape of code — module boundaries, the types that cross them, signatures, and a cited call graph — for code that already exists or a change about to be built.

    739 GitHub stars~2.5k tokensUpdated 5 days ago
    Auto-check passed
  • Structure Codebase

    citypaul/.dotfiles

    Design, audit, and evolve physical source and package structures that expose real architectural boundaries while keeping related behavior together.

    739 GitHub stars~4.4k tokensUpdated 5 days ago
    Auto-check passed
  • Test Design Reviewer

    citypaul/.dotfiles

    Review test quality using Dave Farley's eight properties of good tests.

    739 GitHub stars~1k tokensUpdated 5 days ago
    Auto-check passed
  • Characterisation Tests

    citypaul/.dotfiles

    A skill your agent uses when modifying existing code that lacks tests and you need to document its actual current behavior before making changes -- the legacy code dilemma where you need tests to…

    739 GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check passed
  • Double Check

    citypaul/.dotfiles

    Get a rigorous read-only second opinion on finished work through the host's available reviewer capabilities, preferably from a different model provider.

    739 GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check passed

Works with

Questions about CI Debugging

What does CI Debugging do?

Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis. dotfiles. Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis.

When should I use CI Debugging?

CI Debugging fits situations like: GitHub Actions workflow; build job fails; tests pass locally but fail in CI; diagnosing flaky tests.

How do I install CI Debugging in Claude Code?

Run `npx skills add citypaul/.dotfiles --skill ci-debugging -a claude-code`. Or copy the skill folder (claude/.claude/skills/ci-debugging in citypaul/.dotfiles) into .claude/skills/ci-debugging in your project. Claude Code loads it when a task matches its description.

How do I install CI Debugging in Codex?

Run `npx skills add citypaul/.dotfiles --skill ci-debugging -a codex`. Or copy the skill folder (claude/.claude/skills/ci-debugging in citypaul/.dotfiles) into .agents/skills/ci-debugging in your project. Codex loads it when a task matches its description.

Can I use CI Debugging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add citypaul/.dotfiles --skill ci-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-debugging, .gemini/skills/ci-debugging, .github/skills/ci-debugging and .opencode/skills/ci-debugging in your project.

What does CI Debugging need to run?

Going by SKILL.md and its folder, CI Debugging needs the command-line tools its instructions call (gh, node and npm).

Does CI Debugging access the network?

SKILL.md contains no URLs. Its commands use gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is CI Debugging safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does CI Debugging use?

CI Debugging has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does CI Debugging use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CI Debugging?

Skills that share tags, products or a category with CI Debugging: CI/CD Failure Troubleshooting (ruby-git/ruby-git, 1.8k stars), CI Workflow Guide (sgl-project/sglang, 37k stars), Debugging CI Failures (PostHog/posthog-foss, 721 stars) and CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Debugging?

citypaul (a GitHub user) maintains it in citypaul/.dotfiles, which has 739 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 2, 2026.

Source: citypaul/.dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.