completion-gate

Estrelas13

Forks1

Atualizado26 de março de 2026 às 01:18

Mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

giulio-leone

giulio-leone/harness-os

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	completion-gate
description	Mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.

Universal Completion Gate Skill

Purpose

Enforce a mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.

Use when

Closing an issue
Marking a milestone as done
Opening/merging a PR

Mandatory Gate (no exceptions)

Double consecutive review: two full consecutive passes in the same session with 0 errors, 0 warnings, and no code changes between the two passes. Both passes must be recorded as evidence.
Complete Audit: After passing the two consecutive reviews, perform a comprehensive audit to verify that everything went as expected and the desired outcome is fully achieved.
Fix all new issues and all pre-existing issues in touched scope.
Lint/type-check/build/static analysis pass with 0 errors/0 warnings.
Required tests pass (unit, integration if applicable, E2E if applicable, non-regression).
Full suite passes; coverage is not below baseline.

Procedure

Run full review/check suite (= Pass 1).
If any error/warning exists, fix and restart from step 1 (counter resets).
If Pass 1 is clean, immediately run the suite again without modifying code (= Pass 2).
If Pass 2 is also clean, record both results as gate evidence and mark status done/merge.
If Pass 2 fails, investigate the flaky/non-deterministic cause, fix, and restart from step 1.

Done Criteria

Two consecutive clean review passes are documented.
No unresolved pre-existing issues in touched scope.

Harness Verification

When using the harness-lifecycle pattern, an additional rule applies:

A feature is only "passes": true in feature_list.json if a real test execution (unit, integration, or e2e) confirms it works. Code review alone is insufficient. The agent must have run the tests, not just inspected the code.

Related Skills

testing-policy — defines the required test layers (unit/integration/E2E/non-regression) that must pass during this gate
harness-lifecycle — defines the two-phase lifecycle that uses this gate for feature verification

Anti-patterns

Single-pass approval
Ignoring warnings
Deferring known issues to “later”

Mais deste repositório

mesmo repositório

context-management

giulio-leone/harness-os

Rules and strategies for managing agent context window size, avoiding bloat, and preserving signal-to-noise ratio.

2026-04-0213

error-handling-patterns

giulio-leone/harness-os

Standard patterns for error handling, retry logic, circuit breakers, and graceful degradation.

2026-04-0213

policy-coherence-audit

giulio-leone/harness-os

Detect and remove contradictions across agent policies before execution.

2026-04-0213

programmatic-tool-calling

giulio-leone/harness-os

Multi-step tool workflows via code orchestration to reduce latency, context pollution, and token overhead.

2026-04-0213

prompt-contract-bindings

giulio-leone/harness-os

Bind project-specific prompts to local schema and workflow artifacts while keeping the harness core generic and globally reusable.

2026-04-0213

session-lifecycle

giulio-leone/harness-os

Operational session protocol for task-scoped leases, reconciliation, checkpoints, inspection, queue promotion, and handoff across long-running work.

2026-04-0213

Universal Completion Gate Skill

Purpose

Enforce a mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.

Use when

Closing an issue

Marking a milestone as done

Opening/merging a PR

Mandatory Gate (no exceptions)

Double consecutive review: two full consecutive passes in the same session with 0 errors, 0 warnings, and no code changes between the two passes. Both passes must be recorded as evidence.

Complete Audit: After passing the two consecutive reviews, perform a comprehensive audit to verify that everything went as expected and the desired outcome is fully achieved.

Fix all new issues and all pre-existing issues in touched scope.

Lint/type-check/build/static analysis pass with 0 errors/0 warnings.

Required tests pass (unit, integration if applicable, E2E if applicable, non-regression).

Full suite passes; coverage is not below baseline.

Procedure

Run full review/check suite (= Pass 1).

If any error/warning exists, fix and restart from step 1 (counter resets).

If Pass 1 is clean, immediately run the suite again without modifying code (= Pass 2).

If Pass 2 is also clean, record both results as gate evidence and mark status done/merge.

If Pass 2 fails, investigate the flaky/non-deterministic cause, fix, and restart from step 1.

Done Criteria

Two consecutive clean review passes are documented.

No unresolved pre-existing issues in touched scope.

Harness Verification

When using the harness-lifecycle pattern, an additional rule applies:

A feature is only "passes": true in feature_list.json if a real test execution (unit, integration, or e2e) confirms it works. Code review alone is insufficient. The agent must have run the tests, not just inspected the code.

Related Skills

testing-policy — defines the required test layers (unit/integration/E2E/non-regression) that must pass during this gate

harness-lifecycle — defines the two-phase lifecycle that uses this gate for feature verification

Anti-patterns

Single-pass approval

Ignoring warnings

Deferring known issues to “later”