github-ci-debug
Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/github-ci-debug && cp -r /tmp/github-ci-debug/examples/plugin-packages/github/skills/github-ci-debug ~/.claude/skills/github-ci-debugSKILL.md
# GitHub CI Debug Use this skill only for GitHub Actions failures. ## Workflow 1. Resolve the repository and Actions run ID from the supplied URL, PR, or current branch context. 2. Call `actions-failure` through the connected GitHub service. 3. Report the run URL, failing jobs, failing steps, and the most likely root cause supported by the returned evidence. 4. If the check belongs to an external provider, report its URL and do not pretend the GitHub service controls it. 5. Propose the smallest fix tied directly to the failing step. 6. When the user asked for a fix, implement it locally and run the relevant local check. 7. Summarize remaining uncertainty and what needs a remote rerun. ## Guardrails - Do not rerun or cancel workflows; those actions are not part of this plugin version. - Do not claim complete log coverage when the service returned only job and step summaries. - Do not change code when the evidence points to an unrelated infrastructure or flaky failure unless the user chooses that scope.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.