quality-gates

Diagnose brepjs quality gate failures and apply sanctioned fixes.

77|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/andymai/brepjs --skill quality-gates-andymai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gates
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/quality-gates
Command: npx skills add https://github.com/andymai/brepjs --skill quality-gates-andymai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork when brepjs local quality gates or npm run validate steps fail, so you do not waste time debugging generic CI errors or accidentally breaking project-wide rules with incorrect workarounds.

Core Features & Use Cases

  • Gate failure decoding: Breaks down error output for every quality gate (typecheck, ESLint, layer boundaries, pattern checker, knip) and provides exact, sanctioned fixes or escape hatches for each common violation, no generic advice.
  • Trap avoidance: Flags high-impact project-specific traps like an unbaselined pattern violation that fails every open PR on merge, and the function-lookup CI diff from adding new *Fns.ts exports, so you avoid costly rework across the team.
  • Use case example: If you are contributing to brepjs and your npm run validate fails with a no-explicit-any ESLint error, this Skill tells you to type the value, or use a sanctioned disable comment only for verified WASM binding type gaps.

Quick Start

Use the quality-gates skill to fix the current npm run validate failure by identifying which gate is red and applying the correct escape hatch for the specific error message you see.

Frequently Asked Questions about quality-gates

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

FAQPage Schema
How do I fix npm run validate failures in a TypeScript project?

Fix npm run validate failures by identifying the red quality gate—typecheck, ESLint, layer boundaries, pattern checker, or knip—and applying the exact fix recipe or sanctioned escape hatch for that specific violation.

What causes an unbaselined pattern violation to fail every open PR on merge?

An unbaselined pattern violation fails every open PR on merge because the pattern checker enforces project-wide architectural rules continuously. You must resolve the violation or update the baseline to avoid costly rework across the team.

Can I use an ESLint disable comment for no-explicit-any errors in TypeScript?

Use a sanctioned ESLint disable comment for no-explicit-any errors only for verified WASM binding type gaps. For all other cases, type the value correctly to pass the quality gate without bypassing project rules.

Why does adding new exports to Fns.ts files cause a CI diff failure?

Adding new Fns.ts exports triggers a function-lookup CI diff failure because the quality gate detects unregistered function signatures. Update the function registry alongside the export to avoid this trap and pass CI.

How do I resolve knip unused export check failures during local development?

Resolve knip unused export check failures by removing the unused exports from your TypeScript codebase or updating the knip baseline if the export is intentionally retained for external API surface reasons.

Does the quality-gates skill provide fixes for layer boundary check violations?

The quality-gates skill provides exact fix recipes and sanctioned escape hatches for layer boundary check violations. It decodes the error output and guides you to restructure dependencies to comply with project-specific rules.