gate

Run consistency fixes and commit only when the status is CLEAN.

11|Updated Dec 28, 2024
One-click install
npx skills add https://github.com/wadvanced/aurora_uix --skill gate-wadvanced
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate
Source: https://github.com/wadvanced/aurora_uix/tree/main/.claude/skills/gate
Command: npx skills add https://github.com/wadvanced/aurora_uix --skill gate-wadvanced

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken style, consistency, or documentation issues from slipping into the repository by enforcing a clean lint/fix gate before any conventional commit happens.

Core Features & Use Cases

  • Runs consistency checks and applies fixes: Orchestrates mix consistency via the gate-fix sub-skill and relies on its terminal status to decide next steps.
  • Blocks or defers commits when plans are pending: If the fixer outputs STATUS: PLAN_PENDING, it stops and surfaces the proposed refactor plan verbatim for user approval before committing.
  • Creates conventional commits only when clean: Invokes gate-commit only when the fixer reports STATUS: CLEAN, otherwise it halts and reports what remains.

Quick Start

Run the gate skill and follow its status outcome by committing only after it reports STATUS: CLEAN.

Frequently Asked Questions about gate

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

FAQPage Schema
How do I prevent lint and documentation issues from being committed to my repository?

To prevent lint and documentation issues from being committed, you need a pre-commit gate that runs consistency checks and blocks conventional commits until the repository reports a clean status.

What happens when a consistency fixer requires a refactor plan before committing?

When a consistency fixer requires a refactor plan, the commit process halts and surfaces the proposed plan verbatim for user approval, preventing any changes from being applied until explicitly accepted.

How do I enforce conventional commits only after formatting and linting pass?

You can enforce conventional commits after formatting and linting pass by orchestrating a deterministic workflow that branches on the fixer's terminal status, invoking the commit step only when a clean status is returned.

Does the gate skill work with CI-safe development workflows?

Yes, the gate skill applies directly to CI-safe development workflows where linting, formatting, and documentation requirements must be strictly enforced before changing repository history.

Why does my automated commit fail when the fixer outputs a blocked status?

Your automated commit fails because the gate forbids committing when the fixer outputs a blocked status, halting the process to report what remaining issues need to be resolved before proceeding.