OpenParable
Skip to content
← Back to skills

QA Phase

Testing & Quality
qa-phase

QA 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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

ArgumentDescriptionExample
[feature]Target feature to test/qa-phase user-auth

Workflow

  1. Context: Read design doc and Check phase analysis
  2. Plan: Generate test plan (L1-L5 items with priorities)
  3. Generate: Create test code files
  4. Execute: Run L1-L5 tests (L3-L5 require Chrome MCP)
  5. 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

  1. Run scripts/qa/pre-release-check.sh via Bash
  2. Parse the output for CRITICAL / WARNING / INFO counts
  3. 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
  4. 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

ScannerDetectsSeverity
dead-codeStale require/import, unused exportsCRITICAL / WARNING
config-auditUnreferenced config keys, hardcoded values, missing pathsCRITICAL / WARNING / INFO
completenessMissing agents, long descriptions, missing effortCRITICAL / WARNING / INFO
shell-escapeBare $N in awk, unescaped backticks, unsafe heredocsCRITICAL / 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

LevelTypeToolChrome Required
L1Unit TestNode.js / Jest / VitestNo
L2API Testfetch / curlNo
L3E2E TestChrome MCPYes
L4UX Flow TestChrome MCPYes
L5Data Flow TestChrome MCP + BashYes

Fallback

Chrome MCP unavailable:

  • L1 + L2 only
  • QA report notes "L3-L5 skipped"
  • QA pass/fail based on L1+L2 results only