code-quality-gate_skill

Overview

This skill enforces complete compliance with code quality standards before commits or pull requests. It runs configured linters, formatters, and type checkers, auto-applies fixes where possible, and blocks changes if residual issues remain. The goal is to prevent regressions and keep the repository consistently formatted and type-safe.

How this skill works

The skill reads quality commands from .claude/workflow-config.json and checks whether the quality gate is required. When enabled, it runs the configured sequence (lint, format, typecheck, tests) or a language-specific pipeline, parses tool output, and generates a concise pass/fail report. If auto-fixes are available, it applies them and re-runs checks before deciding to block or allow the commit/PR.

When to use it

• Before committing code to the repository
• Before creating a pull request
• When automated CI reports quality issues
• On explicit request to validate or gate code quality

Best practices

• Keep .claude/workflow-config.json up to date with project tools and commands
• Enable the quality gate for main and release branches at minimum
• Allow automatic fixes (linters/formatters) to run, then re-check results
• Fail fast: block commits/PRs when checks still report issues after auto-fix
• Include clear, actionable error lines in reports to speed remediation

Example use cases

• Pre-commit hook that runs the quality.all command and blocks commits on failure
• CI step that gates merge to main when any tool reports errors
• Local developer workflow: run the gate before opening a PR to avoid CI failures
• On-demand audit: run the gate when a code review flags suspicious style or type issues