Skill

qa-phase

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.

Bash

testing

code-quality

Install

npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkit

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGlobGrepBashTaskAskUserQuestion

Preview

> Execute QA phase of the PDCA cycle. Automatically runs L1-L5 tests with Chrome MCP integration.

SKILL.md

Similar Skills

using-git-worktrees

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.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars513

Forks130

Last CommitApr 22, 2026

Actions

View Source View Plugin View on GitHub View README

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.sh via 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