Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
Install CI Debug
$ npx skills add Porabuild/Poracode --skill ci-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Porabuild/Poracode ci-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .claude/skills/ci-debug && rm -rf skills-srcUse ~/.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/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .claude/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Porabuild/Poracode --skill ci-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Porabuild/Poracode ci-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .agents/skills/ci-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .agents/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Porabuild/Poracode --skill ci-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Porabuild/Poracode ci-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .cursor/skills/ci-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .cursor/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Porabuild/Poracode.git --path resources/plugins/github/skills/ci-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Porabuild/Poracode --skill ci-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Porabuild/Poracode ci-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .gemini/skills/ci-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .gemini/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Porabuild/Poracode ci-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Porabuild/Poracode --skill ci-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .github/skills/ci-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .github/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Porabuild/Poracode --skill ci-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Porabuild/Poracode ci-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/plugins/github/skills/ci-debug .opencode/skills/ci-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ci-debug" agent skill from https://github.com/Porabuild/Poracode/tree/master/resources/plugins/github/skills/ci-debug into .opencode/skills/ci-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ci-debug- GitHub stars
- 114
- Token cost
- ~522 tokens
- SKILL.md length
- 334 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
- Tasks that involve CI/CD
- SKILL.md covers Find the real failure, Separate the failure from the…, Environment differences and Fix and verify, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
CI Debug is an agent skill from Porabuild/Poracode. Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
Its SKILL.md is about 520 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. It works with GitHub Actions. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve CI/CD
Example prompts
- “/ci-debug”
What it can do on your machine
Read from SKILL.md and the folder at commit bffd89d. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Debug loads about 522 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 334 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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
The full file from Porabuild/Poracode at commit bffd89d, republished under its Apache-2.0 licence (© Porabuild). 334 words, ~522 tokens.
Download SKILL.mdSave it as
.claude/skills/ci-debug/SKILL.md (or your agent's skills folder).- name
- ci-debug
- description
- Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
CI Debug
Find out why a check is failing, from evidence rather than from the check's name.
Find the real failure
Start from the check run, get its job, and read the log. A job summary tells you something failed; the log tells you what.
Scan for the first failure, not the loudest one. A long red log is usually one root cause followed by cascading noise — later errors are often just the same failure surfacing again downstream.
Note the step, the command, and the exact error text. Copy the error verbatim; do not paraphrase it into something that sounds cleaner than it was.
Separate the failure from the change
Before blaming the diff, check whether the same job fails on the base branch or on unrelated recent runs. Flaky and pre-existing failures look identical to real ones in a single run.
Say explicitly which of these you concluded:
- the change caused it,
- it was already broken,
- it is flaky (and what evidence supports that),
- you could not tell from the available logs.
"I could not tell" is a legitimate answer. An invented root cause is not.
Environment differences
When something passes locally and fails in CI, compare the things that actually differ: OS and runner image, tool and dependency versions, environment variables and secrets, working directory, and whether the job runs against a merge commit rather than the branch head.
Fix and verify
Propose the narrowest fix that addresses the root cause. Re-run only the failed jobs when you can. If a re-run is needed to confirm a flake, say that is what you are doing and why.
Do not re-run, cancel, or dispatch a workflow merely to gather more evidence unless the user authorized that GitHub action. When a fix is local, run the closest equivalent check before asking CI to confirm it.
Report
Lead with the root cause and the evidence line from the log. Then the fix. If the fix is unverified because CI has not re-run yet, say so.
© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in resources/plugins/github/skills/ci-debug of Porabuild/Poracode.
Open the folder on GitHubat commit bffd89d
Compare with similar skills
CI Debug 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CI Debug this skillPorabuild/Poracode | 114 | — | ~522 | Automated safety check: Pass | Apache-2.0 | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Templatesbartstc/vite-ts-react-template | 122 | 13 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
Similar skills
- Official
GitHub Actions Templates
bartstc/vite-ts-react-template
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
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.
More from Porabuild/Poracode
All 21 skills in this repoInteractive Testing
Porabuild/Poracode
Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.
Release Notes
Porabuild/Poracode
Write consistent, hand-written-looking changelog entries for a Poracode release.
Skill Creator Poracode
Porabuild/Poracode
Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.
App Controls
Porabuild/Poracode
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.
Chrome Control
Porabuild/Poracode
Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.
Computer Use
Porabuild/Poracode
Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.
Related
Works with
Categories
Questions about CI Debug
What does CI Debug do?
Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure. CI Debug is an agent skill from Porabuild/Poracode. Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
When should I use CI Debug?
CI Debug fits situations like: tasks that involve CI/CD.
How do I install CI Debug in Claude Code?
Run `npx skills add Porabuild/Poracode --skill ci-debug -a claude-code`. Or copy the skill folder (resources/plugins/github/skills/ci-debug in Porabuild/Poracode) into .claude/skills/ci-debug in your project. Claude Code loads it when a task matches its description.
How do I install CI Debug in Codex?
Run `npx skills add Porabuild/Poracode --skill ci-debug -a codex`. Or copy the skill folder (resources/plugins/github/skills/ci-debug in Porabuild/Poracode) into .agents/skills/ci-debug in your project. Codex loads it when a task matches its description.
Can I use CI Debug 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 Porabuild/Poracode --skill ci-debug -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-debug, .gemini/skills/ci-debug, .github/skills/ci-debug and .opencode/skills/ci-debug in your project.
What does CI Debug need to run?
SKILL.md names no scripts, command-line tools or credentials: CI Debug is instructions for the agent only.
Does CI Debug access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is CI Debug safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does CI Debug use?
CI Debug is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CI Debug use?
About 522 tokens (SKILL.md is roughly 2.1k 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 Debug?
Skills that share tags, products or a category with CI Debug: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CI Debug?
Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.