skills/quality-gates/SKILL.md
Use when defining definition of done, setting release criteria, or building automated quality checks into the CI/CD pipeline
npx skillsauth add kienbui1995/magic-powers quality-gatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When establishing what "done" means, preventing low-quality code from reaching production, or reducing manual QA overhead.
Agree team-wide: a story is done only when ALL of these pass:
DoD applies to every story — no exceptions without explicit team agreement.
Pipeline structure:
PR opened → lint → unit tests → build
→ integration tests
→ security scan (Snyk/Semgrep)
→ coverage check (must not drop below threshold)
→ [merge gated on all passing]
Merge to main → E2E tests → staging deploy → smoke tests
→ [production deploy gated on all passing]
Before any production release:
Some gates should block unconditionally:
Make these non-negotiable and enforce in CI — not as optional warnings.
content-media
Use when designing for XR (AR/VR/MR), choosing interaction modes, or adapting 2D UI patterns for spatial computing
testing
Use when creating new skills, editing existing skills, or verifying skills work before deployment
development
Use when you have a spec or requirements for a multi-step task, before touching code
development
Use when executing a structured workflow — select and run a feature, bugfix, refactor, research, or incident template with correct agent and model assignments per phase.