quality-gate

Check modified releases against canonical doctrine, repo boundaries, and regression risk.

Updated Aug 27, 2026

Search Tags:#validation #quality #code-review #boundaries #canon #gate #non-regression

Ready to run

npx skills add https://github.com/Deadpool042/Creatyss --skill quality-gate-deadpool042

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/quality-gate
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill quality-gate-deadpool042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a strict final review of a modified batch against canonical doctrine, repository boundaries, and non-regression, reducing risk before validation or deployment.

Core Features & Use Cases

Boundary verification to ensure changes stay within the defined perimeters and align with the doctrine.
Architecture and repository coherence checks to confirm the changes map to the intended system model.
Non-regression detection with targeted guidance to remediate issues quickly.
Use Case: prior to merge, run the gate to obtain a pass/fail verdict and an actionable remediation plan.

Quick Start

Run the quality gate on the modified lot to obtain a verdict and recommended fixes.

Frequently Asked Questions about quality-gate

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

FAQPage Schema

How do I prevent code regression before merging a feature branch?▼

To prevent code regression before merging, you can run a quality gate to check modified releases against canonical doctrine, repo boundaries, and regression risk. It enforces scope boundaries, public contracts, typecheck, lint, and targeted tests to ensure no regression.

What is a quality gate for checking repository boundaries and architectural coherence?▼

A quality gate for repository boundaries is a strict final review that verifies modified code stays within defined perimeters and aligns with the intended system model. It checks architecture and repository coherence to confirm changes map to canonical doctrine.

How do I enforce scope boundaries and public contracts on a pull request?▼

You enforce scope boundaries and public contracts on a pull request by applying a quality gate to the modified lot. This provides a pass or fail verdict based on boundary adherence, typecheck, lint, and targeted tests.

Can I get an actionable remediation plan when non-regression detection fails?▼

Yes, when non-regression detection fails, the quality gate provides targeted guidance to remediate issues quickly. You obtain a pass or fail verdict alongside an actionable remediation plan prior to validation or deployment.

Does the quality gate work with code changes and feature branches directly?▼

Yes, the quality gate works directly with code changes, feature branches, and PR scopes where boundary adherence and architectural coherence are critical. It applies strict final review to these modified batches to reduce deployment risk.

What is the best way to validate code changes against canonical doctrine before deployment?▼

The best way to validate code changes against canonical doctrine is to run a strict quality gate on the modified batch. It checks repository boundaries and non-regression, reducing risk before validation or deployment by providing a clear verdict.