ci-gate

Run detected CI checks locally and print a pass/fail summary.

3|1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/indrasvat/claude-code-skills --skill ci-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-gate
Source: https://github.com/indrasvat/claude-code-skills/tree/main/skills/ci-gate
Command: npx skills add https://github.com/indrasvat/claude-code-skills --skill ci-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run every CI check locally to validate code changes before pushing, surfacing a clear pass/fail status to prevent broken builds in PRs.

Core Features & Use Cases

  • Detects project type from markers (go.mod, package.json, Cargo.toml, pyproject.toml) and runs the appropriate checks in parallel.
  • Reports a concise pass/fail summary table and provides detailed logs for failed checks.
  • Supports adjusting checks via flags to adapt to different teams' CI configurations.

Quick Start

Run the ci-gate skill to validate all CI checks for your current repository.

Frequently Asked Questions about ci-gate

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

FAQPage Schema
How do I run CI checks locally before pushing code to prevent broken PRs?

Running CI checks locally detects project stacks from markers like go.mod or package.json, executes checks in parallel, and presents a fail-fast pass/fail summary to prevent broken PRs.

What is the best way to validate multi-language projects locally in parallel?

Validating multi-language projects locally in parallel is best done by detecting stacks from markers like Cargo.toml or pyproject.toml, ensuring prerequisite tools are available, and executing per-stack checks simultaneously to capture exit codes and durations.

Does local CI validation work with Go, JS/TS, Rust, and Python repositories?

Yes, local CI validation works with Go, JS/TS, Rust, and Python repositories by detecting stacks from markers like go.mod, package.json, Cargo.toml, and pyproject.toml to run the appropriate checks in parallel.

How do I get a unified pass/fail summary table for local code quality checks?

To get a unified pass/fail summary table for local code quality checks, execute detected CI checks in parallel, capture exit codes and durations, and print a concise summary table with verbose logs provided only for failed checks.

Can I adjust local CI checks to adapt to different teams' configurations?

Yes, you can adjust local CI checks to adapt to different teams' configurations by using flags to modify the execution of detected checks across multi-language projects.

Why does local CI execution fail if prerequisite tools are not available?

Local CI execution fails when prerequisite tools are unavailable because the parallel runner requires specific stack tooling to execute per-stack checks and capture accurate exit codes and durations for the summary table.