ci-workflow

Runs the full local frontend CI suite through profile-mapped make targets and drives every check to green.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill ci-workflow-vilnacrm-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-workflow
Source: https://github.com/VilnaCRM-Org/claude-plugins/tree/main/plugins/react-frontend-sdlc/skills/ci-workflow
Command: npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill ci-workflow-vilnacrm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend teams need every quality gate — formatting, linting, type checking, tests, mutation, visual, and Lighthouse — to pass before committing, but running and fixing each check manually is slow and error-prone. This Skill orchestrates the entire local CI loop through the repository's make targets and fixes failures at the root cause until everything exits green. ## Core Features & Use Cases - Full CI orchestration: Executes the profile-mapped make.ci target covering format, ESLint, TypeScript, markdownlint, jscpd, metrics, dependency-cruiser, unit, integration, E2E, visual, mutation, and Lighthouse checks. - Guided failure remediation: Maps each failing check to a concrete fix strategy and a companion skill (code-organization, complexity-management, architecture, testing, accessibility). - Capability-aware degradation: Skips visual, mutation, or Lighthouse lanes with explicit notes when the profile disables those capabilities, and enforces a 5-iteration fix cap before escalating. - Use Case: Before finishing a React/TypeScript pull request, run the CI workflow to validate all quality gates, automatically fix an ESLint violation and a failing Jest suite, and re-run until make ci exits 0. ## Quick Start Ask the AI to run the full frontend CI checks and fix any failures before committing your React/TypeScript changes.

Frequently Asked Questions about ci-workflow

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

FAQPage Schema
How do I run all frontend CI checks locally before committing?▼

Run the make target mapped to make.ci in the profile, which executes formatting, linting, type checking, tests, mutation, visual, and Lighthouse gates. The task is complete only when that target exits with status 0.

How to fix failing ESLint or TypeScript checks in a CI pipeline?▼

Re-run the mapped make.lint_eslint or make.lint_tsc target, then fix the reported rule or type contract at the root cause. Never use eslint-disable or @ts-ignore suppressions to silence failures.

Can I skip visual or mutation testing if my project does not support it?▼

Yes, when the profile sets capabilities.visual_testing or capabilities.mutation_testing to false, those lanes are skipped with an explicit capability-absent note. All other mapped checks still run and must pass.

Why should quality tools run through make targets instead of directly?▼

The make targets wrap the containerized toolchain and bun-managed dependencies, ensuring consistent versions and environments. Invoking ESLint, tsc, Jest, Playwright, Stryker, or Lighthouse directly on the host bypasses that controlled setup.

What happens if CI checks keep failing after multiple fix attempts?▼

The fix loop is bounded at a maximum of 5 iterations. On exhaustion, the process stops and escalates by reporting the still-failing checks, the fixes attempted, and the recommended next step.