qa
QA lead that runs tests, finds edge cases, writes regression tests for every bug found, and verifies fixes. Bootstraps test frameworks if none exist. Use when: "test this", "qa", "find bugs", "run tests", "check quality", or after /review and before /ship.
- License 许可
- MIT
- 所属仓库
- kalash33/kstack
- 最近更新
- 2026-05-20
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- qa
- description
- QA lead that runs tests, finds edge cases, writes regression tests for every bug found, and verifies fixes. Bootstraps test frameworks if none exist. Use when: "test this", "qa", "find bugs", "run tests", "check quality", or after /review and before /ship.
03 SKILL.md 正文
/qa — QA Lead
Find bugs before users do. Every fix gets a regression test.
When to Use
- After implementing a feature
- After
/reviewflags issues - Before
/ship - When you suspect edge cases
Process
Step 1: Detect Test Framework
Auto-detect what's available:
package.json→ Jest, Vitest, Mocha, Playwrightpytest.ini/pyproject.toml→ pytestgo.mod→ go testCargo.toml→ cargo test- Nothing? → Bootstrap one (ask user which)
Step 2: Run Existing Tests
# Run the test suite, capture output
{test_command} 2>&1
Report: X passed, Y failed, Z skipped. Coverage: N%.
Step 3: Analyze for Gaps
Read the diff and identify:
- New functions without tests
- Changed logic without updated tests
- Edge cases: null, empty, boundary values, concurrent access
- Error paths: what happens when things fail?
Step 4: Write Missing Tests
For each gap, write a test that:
- Has a clear name describing the scenario
- Tests ONE thing
- Includes the edge case that would catch a regression
- Follows the project's existing test patterns
Step 5: Run Again
Run the full suite including new tests. If anything fails:
- Diagnose the failure
- Fix the code (not the test, unless the test is wrong)
- Commit the fix atomically
- Re-run to verify
Step 6: Report
## QA Report
Tests: 42 → 51 (+9 new)
Coverage: 83% → 87% (+4%)
Bugs found: 2
Bugs fixed: 2
### New Tests
- test_notification_empty_payload (edge case)
- test_notification_duplicate_delivery (race condition)
- ...
### Bugs Fixed
- 🐛 Empty payload caused crash → now returns 400
- 🐛 Duplicate delivery on retry → added idempotency key
Chaining
- Before:
/review(review findings inform what to test) - After:
/ship(won't ship if tests fail)
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.