​
/gate-check — Validate Advance Phase

Skill mới trong bộ claudekit — Phase gate validation. Kiểm tra ready advance từ design → dev, dev → QA, QA → production. Verdict: PASS (all green) / CONCERNS (risk accepted) / FAIL (blockers). Structured gating, no guessing.

​
Tổng quan

/gate-check quy trình checkpoint trước phase shift. Verify: required artifacts exist, quality gates pass, no critical blockers, team aligned. Khi dùng: Design → dev (“finalized?”), dev → QA (“test coverage ≥ 80%?”), QA → prod (“security audit passed?”), any major transition.

​
Prefix & flags

​
Workflow

1

Auto-detect phase

2

Specific phase check

3

Interpret verdict

PASS: Safe to advance. CONCERNS: Risk documented, proceed or not. FAIL: Critical blockers, don’t advance.
4

If CONCERNS — document + decide

Review PDF, document risks, team agrees, proceed with awareness.
5

If FAIL — fix blockers + recheck

Fix, then: /gate-check --phase production

​
Ví dụ

​
Ready for QA ✓ PASS

Output: Development complete, code reviewed, test coverage 85%, no critical bugs.

​
Not ready for production ✗ FAIL

Output: Critical blockers — security audit not run, test coverage 62% (need 80%), performance SLA unmet. Fix before advance.

​
Ready with risks ⚠ CONCERNS

Output: All gates pass except 2 low-priority UI bugs known (for post-launch patch). Documentation 80% complete (20% by Friday). Proceed with risks documented.

​
Strict mode — no gray areas

Treats CONCERNS as FAIL. Either all green or fail.

​
Force override (hotfix)

Documented for audit trail.

​
Required artifacts per phase

Design → Dev:
  • Design spec (DESIGN.md), Figma/prototype, a11y review, AC per story
Dev → QA:
  • Code review (approved), test coverage ≥ 80%, perf baseline, no critical bugs, staging ready
QA → Production:
  • Security audit (CSO), test coverage ≥ 90%, canary metrics defined, rollback documented, SLAs met, docs complete

​
So sánh skill khác

​
Common pitfalls

  • Run gate-check too late: Should be gate keeper, not post-mortem. Check before shift, not after.
  • Skip FAIL verdict: FAIL = critical blockers. Fix first, not skip.
  • Ignore CONCERNS: Yellow = risks. Document + agree, don’t silently proceed.
  • Ambiguous gates: “Test coverage ≥ 80%” clear. “Good quality” not. Define gates upfront.
  • Perfectionism: CONCERNS OK if risks acceptable. Don’t delay forever.

​
FAQ

Not recommended. FAIL = critical blockers. Fix or escalate for team decision.
Non-blocking warnings. Safe if team agrees to risks + documents them.
Yes: CI runs gate-check, reports verdict. Human reviews + decides (especially CONCERNS).
Yes: /gate-check --override "reason". Logged for audit. Use sparingly (escape hatch).
Phase transitions only. Before design → dev, dev → QA, QA → prod. Not per-commit.

​
Xem thêm