gate-check

Automate repository gate checks for drift and policy violations.

6|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/nesquikm/dev-process-toolkit --skill gate-check-nesquikm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-check
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/gate-check
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill gate-check-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate-check automates comprehensive repository validation to surface drift, policy violations, and setup gaps that threaten release quality.

Core Features & Use Cases

  • Conformance probes: validate root spec hygiene, tracker identity, traceability, and milestone alignment across specs, plans, and FRs.
  • Pre-PR governance: detects drift before merges by surfacing failures and notes that guide fixes.
  • Docs and setup hygiene: ensures the CLAUDE.md, docs navigation, and audit sections are present and correctly stated.

Quick Start

Run the gate-check to validate repository conformance and surface actionable issues before opening a PR.

Frequently Asked Questions about gate-check

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

FAQPage Schema
How do I automate repository gate checks for pull requests?

Automate repository gate checks by running validation probes to surface drift, policy violations, and setup gaps before merging pull requests. This ensures strict traceability and milestone integrity across functional requirements, plans, and specs.

What is traceability conformance validation in software engineering?

Traceability conformance validation is the process of verifying milestone alignment and binding integrity across functional requirements, plans, and specifications. It surfaces drift and policy violations to guarantee release quality before milestones.

How do I check repository hygiene and docs setup before a release?

Check repository hygiene by auditing root spec files, docs navigation, and audit sections. This validates that setup requirements are correctly stated and present, returning structured notes for any compliance failures.

Does gate-check work without external dependencies?

Yes, gate-check works without external dependencies. It independently applies conformance probes to validate tracker identity, root hygiene, and docs compliance, returning structured notes to guide fixes for any detected failures.

What is the best way to detect policy violations before merging code?

The best way to detect policy violations before merging code is to automate pre-PR governance probes. This surfaces drift and setup gaps across tracker identities and plans, returning structured notes that guide necessary fixes.