aiox-apply-qa-fixes
Apply QA gate findings then hand back for re-review. Never self-approves or closes. Use when: apply QA fixes, remediate gate FAIL/CONCERNS, /apply-qa-fixes.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Apply QA gate findings then hand back for re-review. Never self-approves or closes. Use when: apply QA fixes, remediate gate FAIL/CONCERNS, /apply-qa-fixes.
Run AIOX quality gates (lint, typecheck, test, pre-push). Use before commit/push, when checking work quality, or /aiox-quality-gates.
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, *qa-gate, /review-story.
Unified CodeRabbit CLI execution via WSL with self-healing loop. Use this skill when running automated code review before commits, PRs, or QA gates. Handles WSL wrapper, severity filtering, and auto-fix iterations.
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, *qa-gate, /review-story.
Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every other. Also catches missing keyboard navigation, bullet-dump / wall-of-text failure modes, broken self-containment (external link/script/img). Patches the file in place; never changes the original content (slide text, numbers, named entities are the author's work, not yours).
Write, fix, and update integration tests (*.integration.test.ts) for MetaMask Mobile using the tests/integration/ framework. Use when creating a new integration test file, fixing a failing integration test, updating tests after a controller change, or creating / extending a per-domain harness.
Generate comprehensive e2e tests for Lowdefy blocks using Playwright. Use when creating end-to-end tests for block functionality, testing block rendering, properties, events, and user interactions.
Unit-testing conventions specific to src/NodaTime.Test (and sibling .Test projects) in this repo — partial test classes split by concern, TestHelper contract testers for equality/comparison/operators, CultureSaver, TestCase/TestCaseSource data patterns, XML round-trip assertions. Use when writing or reviewing tests under src/NodaTime.Test, src/NodaTime.TzdbCompiler.Test, or src/NodaTime.Test.Console.
Multi-language codebase health scanner. Use when the user explicitly asks to run desloppify, scan for technical debt, get a health score, or create a cleanup plan. Do NOT trigger for general code review, renaming, or fixing individual bugs.