From bkit
Automates PDCA QA phase: L1-L5 test planning, code generation, execution with Chrome MCP (L3-L5), pre-release scans via Bash scripts, and reporting to docs/05-qa.
npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkitThis skill is limited to using the following tools:
> Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
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: