gate-quality

Deploy lint, type-check, and test gates from a controls register into editor, pre-commit, and CI.

1|Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Eaiger-Ent/ee-standard --skill gate-quality-eaiger-ent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gate-quality
Source: https://github.com/Eaiger-Ent/ee-standard/tree/main/plugins/control-register/skills/gate-quality
Command: npx skills add https://github.com/Eaiger-Ent/ee-standard --skill gate-quality-eaiger-ent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories often believe lint, type checking, and tests block merges when the wiring is incomplete or unenforced. This Skill deploys the LNT-001, TYP-001, and TST-001 controls from a controls.yaml register into a target repository and verifies the result with the same checker that audits it. ## Core Features & Use Cases - Register-driven deployment: Reads the linter, type checker, strictness keys, coverage keys, and accepted test commands from controls.yaml rather than hard-coding any tool or version. - Three-locus wiring: Writes the editor extension and file-type binding, pre-commit and pre-push hooks, and CI workflow steps, each carrying a provenance stamp naming its control. - Self-verification: Runs register-check against LNT-001, TYP-001, and TST-001 after writing and reports the verdict exactly as given, including failures. - Use Case: Point the Skill at a repository that has adopted the ee-standard register, and it pins the linter and type checker in the lockfile, enables strict mode, wires hooks and CI steps, and proves the gates block. ## Quick Start Ask the AI to deploy gate-quality into the current repository using its controls.yaml register and report the register-check verdict.

Frequently Asked Questions about gate-quality

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

FAQPage Schema
How do I deploy lint and type-check gates into a repository?▼

Run the gate-quality skill against a repository that has a controls.yaml register. It reads the stack's linter, type checker, and test commands from the register, wires editor, pre-commit, and CI loci, then verifies with register-check.

How do I make pre-commit hooks run tests only on push?▼

The skill writes a tests hook with stages set to pre-push, always_run, and pass_filenames false in .pre-commit-config.yaml. This runs the full suite at push time rather than on every commit.

Can gate-quality deploy without a controls.yaml register?▼

No. The skill deliberately takes no opinions of its own; every tool, version, invocation, and config location comes from the register. Without one it stops, because a default would be a second source of truth.

What happens if enabling strict type checking surfaces existing errors?▼

The skill reports the count of existing type errors and stops rather than weakening the setting. TYP-001 declares baseline null, so there is no tolerated list to add them to without a register change.

Why does the skill fail when an invocation is a bare tool name?▼

A bare tool name resolves from PATH instead of the lockfile-pinned artefact, so the gate would verify against whatever global version is installed. The skill stops and asks you to fix the register first.

Is it safe to re-run gate-quality on an already-deployed repository?▼

Yes. Pre-flight reads existing wiring, the skill replaces only its own stamped hooks and steps, and a re-run after a register bump rewrites stamps with the new contract version.