quality-gate

Automate quality gates before commits, PRs, and user confirmations.

1|Updated Aug 10, 2024
One-click install
npx skills add https://github.com/takumi12311123/dotfiles --skill quality-gate-takumi12311123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/takumi12311123/dotfiles/tree/main/.claude/skills/quality-gate
Command: npx skills add https://github.com/takumi12311123/dotfiles --skill quality-gate-takumi12311123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a mandatory quality gate that auto-triggers before critical actions to ensure plan integrity and code quality.

Core Features & Use Cases

  • Auto-triggers before ExitPlanMode, commit, PR, and user confirmation.
  • Executes plan output generation, format/lint/build checks, and codex-review iterations.
  • Integrates with existing workflows to prevent unsafe actions and surface issues early.

Quick Start

Run the quality gate after plan generation to automatically perform checks and codex-review.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I enforce code quality with automated pre-commit checks?

You can enforce code quality by running an automated quality gate that triggers before commits, checking format, lint, and build integrity. This prevents unsafe actions and surfaces code issues early.

What is a mandatory quality gate for pull requests?

A mandatory quality gate for pull requests is an automated barrier that executes format, lint, and build checks. It ensures plan integrity and code quality before a PR is approved.

How do I automate pre-checks before exiting plan mode?

Automated pre-checks trigger before ExitPlanMode by generating plan outputs and running multi-tool checks. This validates plan integrity and code quality before proceeding.

Does the quality gate integrate with existing codex-review workflows?

Yes, the quality gate integrates with existing workflows by running iterative codex-review cycles. It coordinates these reviews alongside format, lint, and build checks to prevent unsafe actions.

How do I prevent unsafe code commits automatically?

You prevent unsafe commits by applying an auto-trigger policy that acts as a quality gate. It coordinates format, lint, and build checks with iterative codex-review workflows before allowing user confirmation.

What are the limitations of auto-triggering pre-checks before critical actions?

Auto-triggering pre-checks before critical actions requires strict guardrails to function effectively. The process depends on completing multi-tool checks and iterative codex-review workflows before allowing commits or PRs.