Ci debugger
Skill stark-ai-de/agent-skills/incubator/skills/repo-maintenance/ci-debugger
Public Agent Skills for Codex operations, Cursor operations, Claude operations, repo maintenance, skill maintenance, productivity, and engineering workflows.
npx -y skills add stark-ai-de/agent-skills --skill ci-debuggerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Diagnose failed CI jobs and build pipelines using small-log, evidence-first debugging. Use when the user shares a failed GitHub Actions, GitLab CI, Vercel, or package-manager build and wants root cause, minimal fix, and regression test guidance.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.0 KB, as published. Nobody here has run it
CI Debugger
Goal
Find the first meaningful CI failure, explain the root cause with evidence, propose the smallest fix, and recommend the validation command that should prevent recurrence.
When to use
- A CI, build, deploy, or package-manager job failed.
- The user provides logs, a run URL, or asks to inspect CI live.
- Long logs need targeted extraction instead of full dumping.
When not to use
- The user asks for broad repo health rather than one failed pipeline.
- The failure requires production incident response beyond CI diagnosis.
- The user wants dependency risk review without a failing job; use
dependency-update-review.
Inputs
- CI provider, workflow/job name, run URL, failed step, and logs.
- Package manager output, build artifacts, test reports, and recent diffs.
- Repo scripts, workflow YAML, and environment requirements.
Inputs to inspect
- Inspect the failed step, first meaningful error, relevant workflow config, package scripts, and changed files.
- Use targeted log excerpts instead of dumping full logs.
Process
- Identify the failed job and failed step.
- Extract the first meaningful error, not the last cascade.
- Search logs with targeted patterns and inspect nearby context.
- Map the failure to code, config, dependency, environment, or infra.
- Propose a minimal fix and a regression validation command.
- Avoid broad rewrites unless the failure proves a systemic issue.
Workflow
Follow the process above and verify the minimal fix locally when possible. Report skipped live CI checks explicitly.
Decision points
- If logs are incomplete, ask for the failed step or run URL.
- If credentials or external services are required, separate local validation from live validation.
- If multiple jobs fail, group by shared root cause before fixing each.
Safety rules
- Do not paste full secrets from logs.
- Do not rerun expensive or write-capable workflows without approval.
- Do not assume downstream failures are separate bugs until the first failure is resolved.
References
Read references/ci-log-reading.md when logs are noisy or very large.
Scripts
No bundled scripts.
Output format
Return:
- Failing job and step
- First meaningful error
- Root cause
- Minimal fix
- Validation command
- Remaining risks
Failure modes
- If logs are missing, request the failed step output or run URL.
- If authentication is needed for live logs, provide local reproduction steps.
- If multiple roots are plausible, rank them by evidence.
Completion criteria
- Root cause is tied to log evidence.
- Proposed fix is scoped to the failure.
- Validation path is explicit.