gate-check

Run typecheck, lint, test, and contract verification gates before pull requests.

1|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/tmart2322/claude-structure --skill gate-check-tmart2322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-check
Source: https://github.com/tmart2322/claude-structure/tree/main/.claude/skills/gate-check
Command: npx skills add https://github.com/tmart2322/claude-structure --skill gate-check-tmart2322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common pain point of incomplete local pre-PR validation that omits critical CI gates (like linting), which leads to avoidable failed CI runs, wasted review cycles, and delayed feature shipping.

Core Features & Use Cases

  • Exact CI Mirroring: Runs the full sequence of mechanical gates defined in your project's documentation (typecheck, lint, full test suite, contract verification, and custom gate scripts) to match CI behavior exactly.
  • Comprehensive Failure Reporting: Collects and reports all failing gate results instead of stopping at the first error, so you can fix all issues in a single pass.
  • CI Coverage Transparency: Explicitly calls out gates that can only run in CI (such as boot smoke tests or end-to-end tests requiring deployed environment variables) so you have full visibility into local validation gaps.
  • Use Case: Before opening a PR for a code change, run this skill to confirm all reproducible local gates pass, ensuring your first CI run is green and eliminating back-and-forth on fixable CI failures.

Quick Start

Use the gate-check skill to run the full mechanical gate sweep for your current uncommitted code changes before opening a pull request.

Frequently Asked Questions about gate-check

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

FAQPage Schema
How do I run pre-PR checks locally to match CI gates and avoid failed pull request runs?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.

Why does my pull request fail CI even when local tests pass?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.

How do I run all pre-PR lint and typecheck gates without stopping at the first error?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.

Can I run end-to-end tests and boot smoke tests locally before opening a pull request?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.

Do I need any specific CI platform dependencies to run local pre-PR validation checks?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.

What is the best way to verify contract compliance and run custom project gates before a PR?

Pre-PR validation prevents avoidable failed CI runs by executing local checks like typecheck and lint before opening a pull request, catching mechanical gate failures early to save review cycles and avoid delayed feature shipping.