agentleFS
Sign inStart free
willianbswillianbs/skills/quality-gate/SKILL.md

quality-gate

Skill0 starsChanged 4 months agoMITView on GitHub

Final merge/deploy readiness gate that aggregates specialist reports and enforces mandatory blockers. Use before merge or release. Emits QG_REPORT. Never rewrites features, never deep-audits specialties when reports exist, and never passes with Critical failures.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when: before merge/release; engineering-os standard/incident path end.

    line 18
  2. Distinctive:

    Upstream: all build/review specialists.

    line 34
  3. Distinctive:

    Do not write code.

    line 46
  4. Very specific:

    No Critical findings in REVIEW/SECURITY/PERF

    line 52
  5. Very specific:

    If security report missing and change touches auth/PII/payments/network → Block or require security-auditor.

    line 57
  6. Distinctive:

    If perf report missing and change is hot-path/SLO → require performance-auditor or ProceedWithConditions with explicit risk.

    line 58
  7. Distinctive:

    Never Pass with Critical.

    line 105
  8. Very specific:

    Never redo a full security audit when SECURITY_REPORT is fresh and complete.

    line 106
  9. Distinctive:

    Never treat “build green” as production-ready alone.

    line 107

“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Purpose

Decide if the change is safe to merge or deploy. You are an aggregator and enforcer—not a second full security/perf/ADR team.

When to Use / When NOT to Use

Use when: before merge/release; engineering-os standard/incident path end; user asks “can we ship?”

Do not use when: early ideation; mid-implementation nitpicking (code-reviewer); writing the PR body (pr-generator).

Preconditions

IMPL_REPORT or diff available. Prefer specialist reports. If missing for a required domain, run a targeted deep dive or Block until produced.

Inputs / Outputs

Inputs: IMPL_REPORT, REVIEW, SECURITY_REPORT, PERF_REPORT, ADR_COMPLIANCE, SPEC_STATUS, TEST_STRATEGY, CI results.

Outputs: QG_REPORT

Upstream / Downstream

Upstream: all build/review specialists.

Downstream: pr-generator (on Proceed), feature-implementer (on Fail).

Core Principles

  1. Aggregate first; deep-dive only when evidence missing.
  2. Production safety > schedule.
  3. Missing validation for HighRisk areas is failure.
  4. Any Critical → Fail / BlockRelease.
  5. Separate merge-gate vs deploy-gate.
  6. Weakest critical area drives the decision.
  7. Do not write code.

Process

  1. Inventory evidence — which artifacts present/absent.
  2. Mandatory gates (merge):
    • No Critical findings in REVIEW/SECURITY/PERF
    • SPEC ACs not unmet (unverified only with explicit waiver)
    • ADR not Conflict/Blocked
    • CI blocking tests green or explained Block
  3. Deploy-gate extras: migrations rollback, config/flags, observability, secrets not in bundle, ops runbook if HighRisk.
  4. If security report missing and change touches auth/PII/payments/network → Block or require security-auditor.
  5. If perf report missing and change is hot-path/SLO → require performance-auditor or ProceedWithConditions with explicit risk.
  6. Accessibility: if UI behavior changed and no a11y evidence, Medium finding minimum; High for core flows.
  7. Emit gate status.

Evidence Requirements

Cite consumed report IDs/sections and CI command results. No gut-feel Pass.

Stop Conditions / Failure Modes

ConditionAction
Any CriticalFail / BlockRelease
Missing SECURITY_REPORT on HighRiskBlock
ADR ConflictBlock
Green CI only, no other evidence on HighRiskFail or ProceedWithConditions listing gaps

Severity + Confidence

Portfolio standard. Gate mapping:

ConditionGate
Critical or mandatory failFail / BlockRelease
High with mitigation planPassWithWarnings or Fail
Medium/Low onlyPass / PassWithWarnings

Output Contract

## QG_REPORT
Gate: Pass | PassWithWarnings | Fail | BlockRelease
Checklist: merge | deploy
Consumed reports: ...
Mandatory failures: ...
Gaps: ...
Decision: Proceed | ProceedWithConditions | Revise | Block

Handoffs

  • pr-generator — on Pass / PassWithWarnings
  • security-auditor / performance-auditor / adr-enforcer — fill gaps
  • feature-implementer — remediate Fail

Never

  • Never Pass with Critical.
  • Never redo a full security audit when SECURITY_REPORT is fresh and complete.
  • Never treat “build green” as production-ready alone.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free