app-controls
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules —…
Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
$ npx -y skills add Porabuild/Poracode --skill ci-debug --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ci-debugContext preview
The summary Claude sees to decide when to auto-load this skill.
Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure.
name: ci-debug description: "Diagnose a failing GitHub Actions check by reading the real logs and finding the first true failure."
Find out why a check is failing, from evidence rather than from the check's name.
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.
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:
"I could not tell" is a legitimate answer. An invented root cause is not.
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.
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.
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.
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.
Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules —…
Create a deliberately staged commit from the current worktree with a clear subject and why-focused body. Use when asked to commit…
Commit and push the current worktree and create or update a pull request with an accurate title, description, verification…
Finalize the current worktree through deep review, manual QA, fixes, checks, commit, push, PR creation or update, and merge after…
Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Use for visible page state,…
Prove a web change actually works by exercising the flow in Poracode's browser and collecting visual, console, and network…