ci-failure — community ci-failure, fintech-app, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for GitHub-focused Agents needing advanced CI failure diagnosis capabilities. 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

sperezintexas sperezintexas
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
26
Canonical Locale
en
Detected Body Locale
en

Perfect for GitHub-focused Agents needing advanced CI failure diagnosis capabilities. 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

Core Value

Empowers agents to analyze workflow files and pipeline summaries, mapping failures to specific jobs and steps using GitHub Actions and CI pipeline data from .github/workflows/ci.yml and docs/ci.md files.

Ideal Agent Persona

Perfect for GitHub-focused Agents needing advanced CI failure diagnosis capabilities.

↓ Capabilities Granted for ci-failure

Diagnosing remote GitHub Actions CI failures
Analyzing pipeline summaries for error identification
Applying repo-specific fixes based on workflow file analysis

! Prerequisites & Limits

  • Requires access to GitHub repository files
  • Limited to GitHub Actions and CI pipelines
  • Needs .github/workflows/ci.yml and docs/ci.md files for analysis

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is ci-failure?

Perfect for GitHub-focused Agents needing advanced CI failure diagnosis capabilities. 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

How do I install ci-failure?

Run the command: npx killer-skills add sperezintexas/fintech-app/ci-failure. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for ci-failure?

Key use cases include: Diagnosing remote GitHub Actions CI failures, Analyzing pipeline summaries for error identification, Applying repo-specific fixes based on workflow file analysis.

Which IDEs are compatible with ci-failure?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for ci-failure?

Requires access to GitHub repository files. Limited to GitHub Actions and CI pipelines. Needs .github/workflows/ci.yml and docs/ci.md files for analysis.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add sperezintexas/fintech-app/ci-failure. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use ci-failure immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

ci-failure

Install ci-failure, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

CI Failure Diagnosis

When the user reports a remote GitHub Actions / CI failure (or pastes a failure from the Actions tab), apply this skill.

1. Load Context First

Read these files immediately to understand this repo’s CI:

  • Workflow: .github/workflows/ci.yml (and .github/workflows/security.yml if the failure mentions security)
  • Pipeline summary: docs/ci.md

Use them to map the failure to a job and step and to apply repo-specific fixes.

2. Identify Job and Step

From the user’s message or pasted log, determine:

  • Job name (e.g. Lint, Type Check, Test, Build, Docker Build, Notify Slack)
  • Step name (e.g. "Run ESLint", "Build application", "Upload build artifacts")

If the user only pastes an error line (e.g. "No files were found with the provided path: .next"), infer the step from the message and the workflow.

3. Map to Fix

Failure / LogJobStepAction
ESLint error, file:lineLintRun ESLintFix the reported file/line; run npm run lint locally.
Type error, tscType CheckRun TypeScript compilerFix the type; run npx tsc --noEmit locally.
Test failure, vitestTestRun testsFix test or app code; run npm test locally.
Build error, Next.js, OOMBuildBuild applicationCheck "Build application" logs; confirm NODE_OPTIONS=--max-old-space-size=4096 in workflow; fix build error or increase memory.
No files .next, upload artifactBuildBuild application / UploadBuild didn’t produce .next; check "Build application" step logs. Ensure workflow has List build output, "Fail if build did not produce .next", and conditional upload (see docs/ci.md).
Docker build failedDocker BuildBuild Docker imageCheck Dockerfile and build-args (MONGODB_URI, MONGODB_DB).
Notify Slack / healthNotify Slack—Check Secrets (SLACK_WEBHOOK_URL) and Variables (APP_URL); see docs/ci.md and readme.

4. Respond

  1. Say which job and step failed (and link to workflow if helpful).
  2. Give a short cause (e.g. "Build didn’t produce .next" or "ESLint error in src/foo.ts").
  3. Suggest a concrete fix (workflow change, code change, or env/secret), using docs/ci.md and .github/workflows/ci.yml as the source of truth.
  4. If the user pasted only one line, ask for the full job log for the failing step if you need it to be precise (e.g. "Paste the full 'Build application' step log from the Build job").

5. Optional: Cursor Rule

For more detail on mapping failures and repo-specific CI, see .cursor/rules/github-ci.mdc (it aligns with this skill and docs/ci.md).

Related Skills

Looking for an alternative to ci-failure or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer