format-gates

Enforce format compliance across STI pipeline blocks with deterministic grep gates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill format-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: format-gates
Source: https://github.com/gapfDev/workflow/tree/main/c1.5/.claude/skills/format-gates
Command: npx skills add https://github.com/gapfDev/workflow --skill format-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prose-based format checks are error-prone and easy to bypass; this skill enforces format rules mechanically using grep gates so formatting is consistently verified at key checkpoints in the STI pipeline.

Core Features & Use Cases

  • Mechanical, grep-based gates that validate format rules across all STI blocks and phase transitions.
  • Preloads into agent context so every gate is available at ON_ENTER, ON_EXIT, and phase transitions.
  • Supports a structured gate taxonomy (U1, U2, U3) that standardizes how format validation is executed before checkpoints.

Quick Start

Preload the format-gates skill in your agent context and run the defined gates at each checkpoint transition to validate formatting before saving.

Frequently Asked Questions about format-gates

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

FAQPage Schema
How do I automate format validation in STI pipelines?

Automate format validation in STI pipelines by preloading format gates into the agent context, which mechanically enforces compliance at checkpoint transitions using deterministic grep checks.

What is the best way to enforce formatting rules at pipeline checkpoints without human error?

The best way to enforce formatting rules without human error is using deterministic grep gates that mechanically validate required frontmatter and section-named formats before phase changes.

How do I apply deterministic gates to ON_ENTER and ON_EXIT transitions?

Apply deterministic gates to ON_ENTER and ON_EXIT transitions by preloading the format-gates skill into your agent context, making validation available at every defined checkpoint.

Do I need frontmatter to use grep-based gates for format compliance?

Yes, frontmatter with a name and description is required for format compliance, as the grep gates specifically check for these elements alongside the structured U1, U2, and U3 section taxonomy.

Why use mechanical grep gates instead of prose-based format checks?

Mechanical grep gates prevent the errors and bypasses common with prose-based checks by standardizing format validation across all STI blocks and phase transitions deterministically.