ci-check

Run local install, build, typecheck, and test steps and verify GitHub Actions status.

182|19|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/adam-s/intercept --skill ci-check-adam-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-check
Source: https://github.com/adam-s/intercept/tree/main/.claude/skills/ci-check
Command: npx skills add https://github.com/adam-s/intercept --skill ci-check-adam-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of local CI checks and mirrors GitHub Actions status to catch issues before pushing. It helps developers ensure their code passes install, build, typecheck, and test steps locally while validating that the branch CI is green.

Core Features & Use Cases

  • Run the same checks locally using the project’s scripts to reproduce GitHub Actions results.
  • Read and compare CI logs to quickly identify failures and patch issues.
  • Use before committing, after pushing, or when asked to check/fix CI to maintain a healthy codebase.

Quick Start

Run the local CI workflow to mirror GitHub Actions checks on your current branch.

Frequently Asked Questions about ci-check

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

FAQPage Schema
How do I run continuous integration checks locally before pushing code?

Run continuous integration checks locally by executing the project's install, build, typecheck, and test scripts to reproduce GitHub Actions results and catch failures before pushing code to your repository.

What is the best way to verify my GitHub Actions branch status is green?

Verify your GitHub Actions branch status is green by querying the GitHub CLI for remote CI results while simultaneously running local install, build, typecheck, and test scripts to ensure codebase safety.

How do I read and compare CI logs to quickly identify test failures?

Read and compare CI logs to identify test failures by analyzing local script execution outputs against expected GitHub Actions results, enabling rapid patching of issues before committing code.

Can I use local CI verification to reproduce GitHub Actions build and test steps?

Yes, local CI verification reproduces GitHub Actions build and test steps by coordinating script execution to run identical install, typecheck, and test workflows locally, ensuring rapid feedback and reproducibility.

Do I need the GitHub CLI installed to check if my branch CI is green?

Yes, checking if your branch CI is green requires the GitHub CLI to query remote status, while local continuous integration verification handles running the build and test scripts on your development machine.

Why does running local checks not match my GitHub Actions continuous integration results?

Local checks not matching GitHub Actions results may stem from environment differences; analyzing local logs against remote CI logs helps coordinate and align the install, build, and test steps for consistency.