skills.rest
I-Onlabs
I-OnlabsCOMMUNITY
Explore all skills by this author →
GitHub

quality-gates

Enforce tests, type checks, linting, and manual verification before marking work complete.

3|1|Updated Dec 21, 2025
Search Tags:#linting#verification#evidence#quality-gates#tests#manual-verification#type-checks
One-click install
npx skills add https://github.com/I-Onlabs/claude-code-skills --skill quality-gates-i-onlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-gates
Source: https://github.com/I-Onlabs/claude-code-skills/tree/main/quality-gates
Command: npx skills add https://github.com/I-Onlabs/claude-code-skills --skill quality-gates-i-onlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before claiming completion, teams risk releasing unverified features, broken builds, or missing proofs. This skill enforces a deterministic completion policy to ensure work is actually done.

Core Features & Use Cases

  • Mandatory Checks: Tests pass, full regression, type checks, and linting are required before completion.
  • Evidence-Based Verification: Requires explicit verification evidence (tests, type checks, manual test results) before marking done.
  • Manual Validation & Documentation: Ensures evidence is recorded and verifiable, supporting compliance and audit trails.

Quick Start

Run the full quality gate checks on your codebase and attach the verification evidence before marking work complete.

Frequently Asked Questions about quality-gates

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

FAQPage Schema
What is evidence-based verification for software readiness?▼

Evidence-based verification requires explicit proof that tests, type checks, and manual validation passed before work is marked done. This prevents releasing unverified features or broken builds by ensuring compliance and audit trails.

Does this quality gate process support manual verification and documentation?▼

You can prevent premature completion of bug fixes and feature development by applying a deterministic completion policy. This requires running full regressions and documenting manual test results before claiming readiness.

What's the best way to require passing tests and linting before completion?▼

Yes, this quality gate process supports manual verification and documentation. It ensures your manual test results are recorded and verifiable, supporting compliance and audit trails before marking work complete.

When do I need to run full regression checks for code reviews?▼

The best way to require passing tests and linting before completion is to enforce a deterministic quality gate policy. This mandates full regression, type checks, and documented evidence to ensure work is actually done.

When do I need to run full regression checks for code reviews?▼

You need to run full regression checks for code reviews whenever marking work done. This ensures tests pass, linting succeeds, and type checks are verified, providing documented evidence that the codebase is stable.

Related Skills

Explore More Software Engineering Skills→
wtthorntonwtthornton
1

tapps-gate

Run the tapps quality gate and report pass/fail with failing criteria.

Community
Intermediate
fredrikaverpilfredrikaverpil
253

code-review

Enforce evidence-based verification gates before claiming code review completion.

Community
Basic
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate