code-quality-gates

Automate documentation, formatting, type-safety, and console-audit quality gates.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill code-quality-gates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality-gates
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/code-quality-gates
Command: npx skills add https://github.com/changoo89/claude-pilot --skill code-quality-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pre- and post-change quality checks to maintain documentation, formatting, type safety, and audit readiness.

Core Features & Use Cases

  • Documentation gate (PreToolUse): blocks creation of undocumented or poorly formatted content.
  • Formatting and type-safety (PostToolUse): auto-formats code and validates TypeScript types after edits.
  • Stop/audit gate: flags console usage and ensures final readiness before completion.

Quick Start

Integrate PreToolUse, PostToolUse, and Stop hooks to automatically gate documentation, format and type-check code, and audit console usage before completion.

Frequently Asked Questions about code-quality-gates

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

FAQPage Schema
How do I automate TypeScript formatting and type safety checks after code edits?▼

You can automate TypeScript formatting and type safety checks by integrating a PostToolUse hook that auto-formats code and validates types immediately after edits are made.

What is a code quality gate and when do I need it in my development workflow?▼

A code quality gate is an automated checkpoint that validates documentation, formatting, type safety, and audit readiness. You need it before creating docs, after coding, and before finalizing work.

How do I prevent undocumented or poorly formatted content from being created?▼

To prevent undocumented or poorly formatted content, implement a PreToolUse documentation gate that blocks creation attempts until content meets the required formatting and documentation standards.

Can I flag console usage and ensure audit readiness before finalizing a development task?▼

Yes, you can flag console usage and ensure audit readiness by applying a Stop hook that performs console-audit checks and validates final readiness before the task is completed.

Do I need any external dependencies to set up pre- and post-change quality checks?▼

No external dependencies are required to set up pre- and post-change quality checks. The gates integrate with optional scripts, references, and assets without needing additional packages.

What's the best way to maintain audit readiness throughout the software engineering process?▼

The best way to maintain audit readiness is automating end-to-end quality gates across development phases, ensuring documentation, formatting, type safety, and console usage are checked continuously.