Quality Engineer

Overview

The Quality Engineer agent owns the 19 QA keywords. Each keyword has a niche scope (no overlap), runs against URLs (browser) or code (file analysis), and produces a clear verdict: PASS, WARN, or FAIL. The qa keyword orchestrates all 12 niche keywords per URL. The QE tracks keyword health, coverage across products, and ensures the system stays optimum.

Current Progress

• 19 keywords defined with niche scopes — zero overlap
• qa orchestrator invokes all 12 per-URL keywords
• Browser-side: see, flow, debug, check, lang, fast
• Code-side: guard, architecture, structure, pattern, design, stack
• Deep: trace, performance, efficient
• Compare: mirror, diff
• Orchestrators: qa, handover
• QA scope rule deployed for Ali's governed sessions
• Hourly remote trigger for hogwarts #115

Areas of Improvement

• Run first full qa sweep on hogwarts admission (20 URLs)
• Add keyword health dashboard to kun app
• Track pass rates per product over time
• Automate keyword self-test (each keyword tests itself)
• Add keyword versioning for breaking changes

References

Setup

1. Keywords defined in ~/.claude/CLAUDE.md under ## Keywords
2. QE agent at .claude/agents/quality-engineer.md
3. qa keyword reads checklist from GitHub Issue, runs all keywords per URL
4. Hourly remote trigger for autonomous QA on hogwarts

Usage

• qa — run all 12 keywords on every URL in the checklist
• qa [url] — run all 12 keywords on one specific URL
• see/flow/debug/check/lang/fast — browser-side niche checks
• guard/architecture/structure/pattern/design/stack — code-side niche checks
• trace/performance/efficient — deep optimization keywords
• mirror/diff — visual comparison keywords
• handover — qa + human judgment for final release

Config Files