菜单
Establish QA testing processes: test strategies, Google Testing Standards, P0-P4 bug tracking, OWASP security, quality metrics, 90% coverage targets. Includes master prompts for autonomous execution and third-party QA team handoff documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maintain an agent-created LoRAIro pull request after creation or after draft-to-ready transition: mark reviewable draft PRs ready, poll CI and review comments with gh, repair failures in the same worktree/session, reply in Japanese, escalate design loops, and squash merge when safe. Use after creating PRs or when asked to continue PR maintenance automation.
Run LoRAIro PR maintenance to completion automatically after an agent creates a PR or a draft PR becomes ready for review: keep polling CI and bot review with gh, repair failures and reply in Japanese in the same worktree, escalate design loops, and squash merge when safe, without waiting for a human to restart each poll cycle. Use right after an agent-created PR exists or transitions draft-to-ready. Do NOT use for human-authored PRs, and do NOT redefine repair/merge/escalation policy here (that lives in agent-pr-maintainer).
Capture LoRAIro design from the wireframes operation prototype or claude.ai/design recreations correctly. Use when syncing/mirroring design, reconciling Qt (.ui) or the DS AppShell with the design, or when nav/tab order, layout, or grouping looks off between the app and the prototype. The prototype's effective state is produced by render-time JS (e.g. restructureNav), so static-HTML grep alone misses it.
Use this skill to generate well-branded interfaces and assets for LoRAIro (a Japanese desktop tool for preparing image datasets for LoRA / fine-tune training), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
PySide6 widget technical implementation for LoRAIro GUI. Covers Signal/Slot patterns, Direct Widget Communication, Qt Designer integration, and async workers. For design intent and aesthetics, use interface-design skill first.
Interface design skill for dashboards, admin panels, apps, and tools. NOT for marketing design. Provides design intent, domain exploration, craft principles, and component-driven design-tool↔code sync. For PySide6/Qt technical implementation, use lorairo-qt-widget skill.
| name | qa-expert |
| version | 1.0.0 |
| description | Establish QA testing processes: test strategies, Google Testing Standards, P0-P4 bug tracking, OWASP security, quality metrics, 90% coverage targets. Includes master prompts for autonomous execution and third-party QA team handoff documentation. |
| keywords | ["qa","testing","test-cases","bug-tracking","google-standards","owasp","security","automation","quality-gates","metrics"] |
Establish world-class QA testing processes for any software project using proven methodologies from Google Testing Standards and OWASP security best practices.
Trigger this skill when:
One-command initialization:
python scripts/init_qa_project.py <project-name> [output-directory]
What gets created:
tests/docs/, tests/e2e/, tests/fixtures/)TEST-EXECUTION-TRACKING.csv, BUG-TRACKING-TEMPLATE.csv)BASELINE-METRICS.md, WEEKLY-PROGRESS-REPORT.md)For autonomous execution (recommended): See references/master_qa_prompt.md - single copy-paste command for 100x speedup.
Initialize complete QA infrastructure with all templates:
python scripts/init_qa_project.py <project-name> [output-directory]
Creates directory structure, tracking CSVs, documentation templates, and master prompt for autonomous execution.
Use when: Starting QA from scratch or migrating to structured QA process.
Write standardized, reproducible test cases following AAA pattern (Arrange-Act-Assert):
assets/templates/TEST-CASE-TEMPLATE.mdTest case format: TC-[CATEGORY]-[NUMBER] (e.g., TC-CLI-001, TC-WEB-042, TC-SEC-007)
Reference: See references/google_testing_standards.md for complete AAA pattern guidelines and coverage thresholds.
Ground Truth Principle (critical):
02-CLI-TEST-CASES.md) = authoritative source for test stepsreferences/ground_truth_principle.md for preventing doc/CSV sync issuesManual execution:
02-CLI-TEST-CASES.md) ← always start hereTEST-EXECUTION-TRACKING.csv immediately after EACH test (never batch)BUG-TRACKING-TEMPLATE.csv if test failsAutonomous execution (recommended):
references/master_qa_prompt.mdInnovation: 100x faster vs manual + zero human error in tracking + auto-resume capability.
File bugs with proper severity classification:
Required fields:
Severity classification:
Reference: See BUG-TRACKING-TEMPLATE.csv for complete template with examples.
Calculate comprehensive QA metrics and quality gates status:
python scripts/calculate_metrics.py <path/to/TEST-EXECUTION-TRACKING.csv>
Metrics dashboard includes:
Quality gates (all must pass for release):
| Gate | Target | Blocker |
|---|---|---|
| Test Execution | 100% | Yes |
| Pass Rate | ≥80% | Yes |
| P0 Bugs | 0 | Yes |
| P1 Bugs | ≤5 | Yes |
| Code Coverage | ≥80% | Yes |
| Security | 90% OWASP | Yes |
Generate QA reports for stakeholders:
Daily summary (end-of-day):
Weekly report (every Friday):
WEEKLY-PROGRESS-REPORT.md (created by init script)BASELINE-METRICS.mdReference: See references/llm_prompts_library.md for 30+ ready-to-use reporting prompts.
Implement OWASP Top 10 security testing:
Coverage targets:
Target: 90% OWASP coverage (9/10 threats mitigated).
Each security test follows AAA pattern with specific attack vectors documented.
For new QA engineers joining a project, complete 5-hour onboarding guide:
Read: references/day1_onboarding.md
Timeline:
Checkpoint: By end of Day 1, environment running, first test executed, ready for Week 1.
Enable LLM-driven autonomous QA testing with single master prompt:
Read: references/master_qa_prompt.md
Features:
Benefits:
Usage: Copy master prompt, paste to LLM, let it run autonomously for 5 weeks.
Access detailed guidelines from bundled references:
references/day1_onboarding.md - 5-hour onboarding guide for new QA engineersreferences/master_qa_prompt.md - Single command for autonomous LLM execution (100x speedup)references/llm_prompts_library.md - 30+ ready-to-use prompts for specific QA tasksreferences/google_testing_standards.md - AAA pattern, coverage thresholds, fail-fast validationreferences/ground_truth_principle.md - Preventing doc/CSV sync issues (critical for test suite integrity)Test case templates and bug report formats:
assets/templates/TEST-CASE-TEMPLATE.md - Complete template with CLI and security examplesAutomation scripts for QA infrastructure:
scripts/init_qa_project.py - Initialize QA infrastructure (one command setup)scripts/calculate_metrics.py - Generate quality metrics dashboard1. python scripts/init_qa_project.py my-app ./
2. Fill in BASELINE-METRICS.md (document current state)
3. Write test cases using assets/templates/TEST-CASE-TEMPLATE.md
4. Copy master prompt from references/master_qa_prompt.md
5. Paste to LLM → autonomous execution begins
1. Read references/master_qa_prompt.md
2. Copy the single master prompt (one paragraph)
3. Paste to LLM conversation
4. LLM executes all 342 test cases over 5 weeks
5. LLM updates tracking CSVs automatically
6. LLM generates weekly reports automatically
1. Read references/google_testing_standards.md (OWASP section)
2. Write TC-SEC-XXX test cases for each OWASP threat
3. Target 90% coverage (9/10 threats)
4. Document mitigations in test cases
1. Ensure all templates populated
2. Verify BASELINE-METRICS.md complete
3. Package tests/docs/ folder
4. Include references/master_qa_prompt.md for autonomous execution
5. QA team can start immediately (Day 1 onboarding → 5 weeks testing)
This skill is effective when: