From bkit — AI Native Development OS
Executes QA phase with L1-L5 test planning, generation, execution, and reporting for a single feature. Includes pre-release quality scans to catch structural issues early.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bkit:qa-phase [feature][feature]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.
Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.
| Argument | Description | Example |
|---|---|---|
[feature] | Target feature to test | /qa-phase user-auth |
docs/05-qa/{feature}.qa-report.mdBefore running L1 tests, execute the automated quality scanners to catch structural issues early.
scripts/qa/pre-release-check.sh via Bash| Scanner | Detects | Severity |
|---|---|---|
| dead-code | Stale require/import, unused exports | CRITICAL / WARNING |
| config-audit | Unreferenced config keys, hardcoded values, missing paths | CRITICAL / WARNING / INFO |
| completeness | Missing agents, long descriptions, missing effort | CRITICAL / WARNING / INFO |
| shell-escape | Bare $N in awk, unescaped backticks, unsafe heredocs | CRITICAL / WARNING |
When scanner results are available, include them in the QA report:
## Pre-Release Scan Results
- **Scanner**: dead-code — 0 CRITICAL, 1 WARNING, 0 INFO
- **Scanner**: config-audit — 0 CRITICAL, 0 WARNING, 2 INFO
- **Scanner**: completeness — 0 CRITICAL, 0 WARNING, 1 INFO
- **Scanner**: shell-escape — 0 CRITICAL, 0 WARNING, 0 INFO
**Overall**: PASS (0 CRITICAL issues)
| Level | Type | Tool | Chrome Required |
|---|---|---|---|
| L1 | Unit Test | Node.js / Jest / Vitest | No |
| L2 | API Test | fetch / curl | No |
| L3 | E2E Test | Chrome MCP | Yes |
| L4 | UX Flow Test | Chrome MCP | Yes |
| L5 | Data Flow Test | Chrome MCP + Bash | Yes |
Chrome MCP unavailable:
npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkitEstablishes QA processes for software projects: test strategies, Google-standard cases (AAA pattern), execution tracking, P0-P4 bug classification, OWASP security testing, quality metrics, reports, autonomous execution, and handoff templates.
Owns the quality gate for features and releases. Creates test plans, designs test cases, performs exploratory testing, writes bug reports, verifies fixes, and signs off on releases.