QA Phase
Testing & Qualityqa-phaseQA Phase is an Agent Skill for testing & quality published in the popup-studio-ai/bkit-claude-code repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/popup-studio-ai/bkit-claude-code/blob/HEAD/skills/qa-phase/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/qa-phase, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
QA Phase Skill
Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.
Arguments
| Argument | Description | Example |
|---|---|---|
[feature] | Target feature to test | /qa-phase user-auth |
Workflow
- Context: Read design doc and Check phase analysis
- Plan: Generate test plan (L1-L5 items with priorities)
- Generate: Create test code files
- Execute: Run L1-L5 tests (L3-L5 require Chrome MCP)
- Report: Generate QA report to
docs/05-qa/{feature}.qa-report.md
PRE-SCAN: Pre-Release Quality Check
Before running L1 tests, execute the automated quality scanners to catch structural issues early.
Steps
- Run
scripts/qa/pre-release-check.shvia Bash - Parse the output for CRITICAL / WARNING / INFO counts
- If CRITICAL issues found:
- Report all CRITICAL issues with file paths and suggested fixes
- Recommend fixing CRITICAL issues before proceeding with L1-L5 tests
- Ask user whether to continue or abort QA phase
- If only WARNING/INFO issues (no CRITICAL):
- Include scanner results in the QA report under "Pre-Release Scan" section
- Continue to L1 test planning
Scanner Coverage
| 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 |
QA Report Integration
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)
Test Levels
| 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 |
Fallback
Chrome MCP unavailable:
- L1 + L2 only
- QA report notes "L3-L5 skipped"
- QA pass/fail based on L1+L2 results only