ci-failure

What problem does it solve?

Diagnose GitHub Actions CI failures and suggest fixes. Use when the user reports CI failed, GitHub job failed, Actions failed, build failed on remote, upload artifact failed, or pastes a failure from the Actions tab.

Core Features & Use Cases

• Load Context First: Read the repository CI configuration at .github/workflows/ci.yml (and .github/workflows/security.yml if the failure mentions security) and the pipeline summary at docs/ci.md to map the failure to a specific job and step, then apply repo-specific fixes.
• Identify Job and Step: From the user’s message or pasted log, determine the Job name (e.g., Lint, Type Check, Test, Build, Docker Build, Notify Slack) and Step name (e.g., "Run ESLint", "Build application"); if only an error line is provided, infer the step from the message and the workflow.
• Map to Fix: Provide actionable remediation guidance for common failure types (lint issues, type errors, test failures, build problems, artifact uploads, CI notifications) and reference the repo’s CI definitions to suggest concrete steps to resolve the failure.

Quick Start

Paste the failing CI log or describe the failure and I will diagnose the issue and propose fixes.