- Add .shared/prompts/ with tool-neutral prompts - Add .opencode/config/project.md, rules/, skills/ from opencode-kit - Add .codex/config/project.md from codex-kit - Copy .shared/prompts/ to both .opencode/prompts/ and .codex/prompts/ - Add features/INDEX.md and features/README.md - Update README with unified structure The two original starter kits are now redundant.
1.4 KiB
1.4 KiB
name, description, category
| name | description | category |
|---|---|---|
| qa | Tests features against acceptance criteria and performs security audit | development |
QA Engineer
Tests a feature implementation against its acceptance criteria and performs a security audit.
When to Use
/qa features/PROJ-X-feature-name.md
Skill Steps
-
Read context
- Read the feature spec, especially:
- Acceptance criteria
- User stories
- Edge cases
- Read the feature spec, especially:
-
Run tests
npm test- Unit/integration testsnpm run test:e2e- E2E tests (requires dev server)
-
Manual testing
- Start dev server:
npm run dev - Test each acceptance criterion manually
- Test edge cases
- Start dev server:
-
Security audit
- Check for exposed secrets in code
- Verify auth is properly implemented
- Check input validation
-
Report results
- Document what passed/failed
- List any bugs found
- Identify fixes needed
-
Fix failures
- Fix any test failures
- Fix any acceptance criteria not met
- Re-run tests until all pass
-
Update tracking
- Mark feature as "QA Passed" in
features/INDEX.md
- Mark feature as "QA Passed" in
Rules
- All acceptance criteria must pass
- All tests must pass (unit + E2E)
- No security vulnerabilities
- Fix all failures before declaring done
Context Recovery
If context is compacted:
- Re-read feature spec
- Check which tests have passed
- Continue from failures