quality-gate

Orchestrates a multi-stage quality gate process for code merging with automated verification, security review, and documentation checks.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill quality-gate-g-zenr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/quality-gate
Command: npx skills add https://github.com/g-zenr/relay-api --skill quality-gate-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the pre-merge quality assurance process, ensuring code meets verification, review, and security standards before being integrated into the main branch.

Core Features & Use Cases

  • Automated Verification: Runs tests and type checks to catch errors early.
  • Code Auditing: Checks for structural issues like layer violations, dead code, and concurrency problems.
  • Security Review: Verifies adherence to security best practices for secret handling and authentication.
  • Documentation Currency: Ensures documentation stays in sync with the codebase.
  • Use Case: Before merging a new feature, run the quality gate to automatically confirm all tests pass, no sensitive information is exposed, and documentation is up-to-date.

Quick Start

Run the full quality gate to verify, review, and audit the code before merging.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I automate pre-merge code quality checks and security audits?

Automating pre-merge code quality and security audits involves orchestrating a multi-stage quality gate process that runs automated tests, checks for dead code, and verifies secret management before code integration.

What is a multi-stage quality gate process in CI/CD?

A multi-stage quality gate in CI/CD is an orchestrated verification workflow that executes automated testing, code quality auditing, security reviews, and documentation currency checks before merging code into the main branch.

How do I check for dead code and concurrency safety before merging?

Checking for dead code and concurrency safety requires running a pre-merge code audit that identifies structural issues, enforces dependency flow, and verifies concurrency safety before code integration.

Can I verify security practices like secret management and input validation automatically?

Yes, verifying security practices like secret management and input validation can be automated through a security review stage within a quality gate that validates adherence to security best practices.

What is the best way to ensure documentation stays in sync with the codebase?

Ensuring documentation stays in sync with the codebase is achieved by running a documentation currency check during the pre-merge quality gate process to verify documentation accuracy before merging code.

Does the quality gate enforce dependency flow and generate audit logs?

Yes, the quality gate enforces dependency flow and ensures observability through audit logs by orchestrating structural code auditing and automated verification during the pre-merge process.