Skip to content
Skills Library
Management & product · Review & audit

gate

/gate

Run a QA AI OS lifecycle gate (idea, validate, spec, build, review, ship, operate, grow, sunset) against the current work — asks the technical AND business questions, collects real evidence, and returns PASS / HOLD / KILL saved to .qa-ai-os/verdicts/. Use when the user says "run the build gate", "is this ready to ship", "gate this", "qa check", or before a review or release.

Repository
vibecheck ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run a QA AI OS lifecycle gate (idea, validate, spec, build, review, ship, operate, grow, sunset) against the current work — asks the technical AND business questions, collects real evidence, and returns PASS / HOLD / KILL saved to .qa-ai-os/verdicts/. Use when the user says "run the build gate", "is this ready to ship", "gate this", "qa check", or before a review or release.

Triggers from the description

run the build gateis this ready to shipgate thisqa check

Arguments

/gate <stage> [what is being gated]
Original author description

Run a QA AI OS lifecycle gate (idea, validate, spec, build, review, ship, operate, grow, sunset) against the current work — asks the technical AND business questions, collects real evidence, and returns PASS / HOLD / KILL saved to .qa-ai-os/verdicts/. Use when the user says "run the build gate", "is this ready to ship", "gate this", "qa check", or before a review or release.

How it works

  1. 1. Pick the gate
  2. 2. Collect evidence — don't assume it
  3. 3. Verdict
  4. 4. Save it
  5. 5. Report
Original SKILL.md headings · 60 lines, 360 words
SKILL.md preview
---
name: gate
description: Run a QA AI OS lifecycle gate (idea, validate, spec, build, review, ship, operate, grow, sunset) against the current work — asks the technical AND business questions, collects real evidence, and returns PASS / HOLD / KILL saved to .qa-ai-os/verdicts/. Use when the user says "run the build gate", "is this ready to ship", "gate this", "qa check", or before a review or release.
argument-hint: "<stage> [what is being gated]"
---

# QA AI OS — gate

## 1. Pick the gate
Stage from the argument; if missing, infer it from the situation (uncommitted
code → build; open PR → review; about to release → ship; a new idea → idea) and
say which you picked. Read `${CLAUDE_PLUGIN_ROOT}/gates/<stage>.md` and
`${CLAUDE_PLUGIN_ROOT}/rules/QUALITY.md`. If the repo's `AGENTS.md` has repo
rules, those apply too.

## 2. Collect evidence — don't assume it
For every question and check in the gate file, get **evidence**:
- run the command and read its real exit code and output (never a pipeline
  ending in `grep`/`tail` — capture the exit code);
- cite `file:line`;
- quote the measured number or the customer's words.

"Looks fine", "should work", and "the AI said it passed" are not evidence. If
you can't get evidence, the item is **missing**, not passed. A check you could
not run is UNKNOWN, and unknown is never PASS.

For business questions, look in the repo first (`core/`, `bets/`, `decisions/`
if it's a Main Branch business repo; README/docs otherwise). Ask the user only
for what the repo can't answer.

Use the repo's reviewer (`roles.reviewer`, see `/qa-ai-os:review`) as a critic
for anything you wrote yourself in this session — the author grading their own
work is the weakest evidence there is. Skip it for MINIMAL changes, and collect
deterministic evidence (commands, file:line) before spending an AI call
(QUALITY.md §0).

## 3. Verdict
- **PASS** — every required item has evidence.
- **HOLD** — list each missing/failed item and the exact action that flips it.
- **KILL** — evidence says stop, or a kill rule set in advance fired.

Never upgrade a verdict to be encouraging. A HOLD with a clear fix list is the
useful outcome.

## 4. Save it
Write `.qa-ai-os/verdicts/YYYY-MM-DD-<stage>-<short-slug>.md` (ask first the
first time; create the folder):

```markdown
---
stage: build
verdict: HOLD
commit: <sha or "uncommitted">
date: YYYY-MM-DD
---
# Build gate — <what>
| # | Check | Result | Evidence |
|---|---|---|---|
## To flip to PASS
```

## 5. Report
Lead with the verdict and the shortest path to PASS, in plain English. Keep the
evidence table in the file, not the chat.

Versions

RepositoryScoreLicence
This page · Vibecheck-QA/vibecheck100MIT
sh5623/e2e-rail100MIT
skillberry-ai/cap-evolve100Apache-2.0
bitIO/wheelhouse100MIT
Perchusha/pitwall100MIT
jease0502/research-agent-kit100Apache-2.0
jeffersonvalente/cardume100MIT
iankiku/forwward-teams100MIT
fdu-ins/insurance-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 1aa7a89ac066 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flow
    Run the buildflow gated build process from idea to real done-evidence. Walk gated stages (Idea->Research->Scope->PRD->ADR->Contract->Cards->Build->Review->Deploy/Ship->Verify->Retro), each with a honest gate that must pass before advancing. Adapts to project type…
  • 90gate-check
    Runs a stage gate (discovery, design, build or launch): checks the required artifacts for the current rigor, collects verdicts from the signing directors and leads, writes a gate report, and on PASS offers to advance the stage. Use when a stage's work looks finished, before…
  • 95gate-check
    Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
  • 95gate-check
    Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
  • 90gate-check
    Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
  • 95gate-check
    Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.