quality-gate

Orchestrates lint, tests, type check, and build for JavaScript/TypeScript projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hemant0510/rwa --skill quality-gate-hemant0510
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/hemant0510/rwa/tree/main/.claude/Skills/quality-gate
Command: npx skills add https://github.com/hemant0510/rwa --skill quality-gate-hemant0510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality gate orchestration that ensures code changes pass through a defined sequence of checks before merging.

Core Features & Use Cases

  • Orchestrates a deterministic sequence: lint, tests, type check, and build to guarantee code health.
  • Supports Variant A (implementation) and Variant B (pre-commit) to suit different development workflows.
  • Provides clear remediation guidance and re-run prompts after failures.

Quick Start

Run the quality gate to execute lint, tests, type-check, and build in order, stopping on first failure.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I enforce pre-commit quality checks for lint, tests, and type checking in JavaScript?

Pre-commit quality checks are enforced by running a deterministic sequence of lint, tests, type-check, and build tasks. This sequence stops on the first failure, ensuring code health before integration in JavaScript and TypeScript projects.

What is a code quality gate and when do I need it for CI workflows?

A code quality gate orchestrates end-to-end checks like lint, tests, and type validation to catch issues early. You need it during development and pre-commit workflows to guarantee code changes pass defined checks before merging into a CI pipeline.

Can I run quality gate checks for both implementation and pre-commit modes?

Yes, quality gate checks support both implementation and pre-commit variants to suit different development workflows. Both modes execute the required lint, tests, type checking, and build validations to verify code health.

What is the best way to automate lint, type-check, and build validation before merging code?

The best way to automate validation is orchestrating a defined sequence of lint, tests, type check, and build tasks. This deterministic approach catches issues early and provides clear remediation guidance and re-run prompts after failures.

Why does my pre-commit quality gate stop running after a lint or type check failure?

The quality gate stops running on the first failure to prevent unnecessary execution of subsequent steps. It provides clear remediation guidance and re-run prompts so you can resolve the specific lint, type check, or test failure before continuing.