fix-ci

Triage and fix format, lint, type-check, and test failures in monorepo CI.

14|5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill fix-ci-thecardgoat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-ci
Source: https://github.com/TheCardGoat/lorcana-simulator/tree/main/.agents/skills/fix-ci
Command: npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill fix-ci-thecardgoat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly restore a failing monorepo CI pipeline by triaging format, lint, type-check, and test failures and then applying the smallest safe fixes without expanding the change scope.

Core Features & Use Cases

  • Failure triage & classification: Groups CI output into format, lint, type, and test buckets to identify the highest-signal problem areas.
  • Scoped fix batching: Applies targeted edits at the file or package level based on error counts, reducing churn while improving convergence.
  • Verification loop: Re-runs targeted package checks after each batch and finishes with the full bun run ci-check to confirm the repo is clean.
  • Blocked tracking: Marks repeatedly failing scopes as blocked after limited attempts and moves on to keep progress going.

Quick Start

Run the skill to triage the output of bun run ci-check, apply the smallest correct bounded fixes, and keep re-verifying until CI turns green.

Frequently Asked Questions about fix-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix monorepo CI failures when bun run ci-check is failing?

Fix monorepo CI failures by triaging format, lint, type-check, and test errors into categories, applying minimal scoped edits at the file or package level, and re-running targeted checks until the full CI pipeline turns green.

What is the best way to triage lint and type-check errors in a Bun monorepo?

Triage lint and type-check errors by parsing CI output, grouping failures by category and file or package, applying the smallest correct bounded fixes, and repeatedly re-running targeted checks to verify convergence without expanding change scope.

Can I use this to fix test failures without modifying lockfile or node_modules?

Yes, you can fix test failures while strictly avoiding lockfile, node_modules, and generated artifacts, ensuring only minimal source edits are applied to resolve the failing tests and restore the CI pipeline.

Why does my CI fix process keep getting stuck on repeated failures?

CI fix processes get stuck when repeatedly failing scopes exceed limited attempts. The workflow marks these scopes as blocked and moves on to other packages to keep progress going, preventing endless loops on unresolvable errors.

Does this CI triage workflow apply to any repository or just specific monorepos?

This CI triage workflow applies specifically to developers working in the the-card-goat-online repository, designed to triage and correct format, lint, type-check, and test errors when bun run ci-check is failing.

What are the limitations of automated CI fix batching in a monorepo?

Automated CI fix batching is limited to scoped minimal edits and bounded attempts, avoiding lockfile, node_modules, and generated artifacts, meaning complex dependency-level failures or structural issues may remain blocked and require manual intervention.