Skill556 estrellas del repoactualizado 11d ago
qa-phase
The qa-phase skill executes the QA phase of the PDCA cycle by automatically running L1-L5 tests on a specified feature. It begins with a pre-release quality scan to detect structural issues, generates a comprehensive test plan prioritizing across five test levels, creates test code files, executes tests using Node.js for L1-L2 and Chrome MCP for L3-L5, and produces a detailed QA report saved to the docs directory. Use this skill to systematically validate features before release.
Instalar en Claude Code
Copiargit clone --depth 1 https://github.com/popup-studio-ai/bkit-claude-code /tmp/qa-phase && cp -r /tmp/qa-phase/skills/qa-phase ~/.claude/skills/qa-phaseDespués abre una sesión nueva de Claude Code; el skill carga automáticamente.
Definición
SKILL.md
# 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
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
| 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:
```markdown
## 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