qa-architect

Audit unit and smoke tests for depth, state validation, and resilience gaps.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/h-4vok/diagram-tours --skill qa-architect-h-4vok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-architect
Source: https://github.com/h-4vok/diagram-tours/tree/main/.agents/skills/qa-architect
Command: npx skills add https://github.com/h-4vok/diagram-tours --skill qa-architect-h-4vok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits unit and smoke tests to ensure meaningful validation, realistic fixtures, and actionable diagnostics, preventing false confidence.

Core Features & Use Cases

  • Pillar-based audit: enforces depth of assertions, side-effect validation, and resilient selectors across tests.
  • Guardrails guidance: surfaces actionable improvements and consistent reporting tags like [CRITICAL], [IMPROVEMENT], and [FRAGILE].
  • Scope-aware reviews: focuses on packages/*/test/*.test.ts and packages/web-player/smoke/*.spec.ts with per-file reports.

Quick Start

Run the QA Architect audit across your repository’s tests to surface depth gaps and actionable recommendations.

Frequently Asked Questions about qa-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit smoke tests for meaningful validation and false confidence?▼

Audit smoke tests by enforcing depth of assertions, side-effect validation, and resilient selectors to surface actionable diagnostics and realistic fixtures, preventing false confidence. Apply the audit across `packages/*/test/*.test.ts` and `packages/web-player/smoke/*.spec.ts` files.

What is test depth gap analysis in unit and smoke tests?▼

Test depth gap analysis identifies missing assertions, inadequate state validation, and fragile selectors within unit and smoke tests. It surfaces actionable diagnostics with consistent reporting tags like [CRITICAL], [IMPROVEMENT], and [FRAGILE] to highlight specific weaknesses.

How do I generate actionable diagnostics for fragile test selectors?▼

Generate actionable diagnostics for fragile selectors by applying a pillar-based audit across your test suites, surfacing improvements with reporting tags like [FRAGILE]. It provides concrete, contract-aligned recommendations referencing `docs/tour-spec-v1.md`.

Does the test audit provide per-file reports for packages?▼

Yes, the test audit provides per-file reports scoped specifically to `packages/*/test/*.test.ts` and `packages/web-player/smoke/*.spec.ts`. This scope-aware review focuses on surfacing depth gaps and actionable improvements within your repository's exact test structure.

Can I use this audit for state validation and side-effect checking?▼

Yes, you can use this audit for state validation and side-effect checking. It enforces a pillar-based audit across your test suites to identify gaps in side-effect validation and state checks, providing concrete recommendations and guardrails for improvements.

What are the limitations of automated test depth auditing?▼

Automated test depth auditing is limited to analyzing existing test files within specified package paths like `packages/*/test/*.test.ts`. It cannot generate new tests autonomously; it only surfaces diagnostics and contract-aligned recommendations referencing `docs/tour-spec-v1.md` for manual implementation.