qaa-agent 1.6.2 → 1.6.3

package/.claude/commands/qa-gap.md

@@ -1,20 +1,20 @@
-# QA Gap Analysis
-
-Compare a developer repository against its QA repository to identify coverage gaps. Requires both repo paths. Produces a detailed gap report showing missing tests, broken tests, and quality assessment.
-
-## Usage
-
-/qa-gap --dev-repo <path> --qa-repo <path>
-
-- --dev-repo: path to the developer repository (required)
-- --qa-repo: path to the existing QA repository (required)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- testing pyramid, test spec rules, quality gates.
-2. Execute the workflow:
-
-Follow the workflow defined in `@workflows/qa-gap.md` end-to-end.
-Preserve all workflow gates (both-repo scanning, gap metrics).
-
-$ARGUMENTS
+# QA Gap Analysis
+
+Compare a developer repository against its QA repository to identify coverage gaps. Requires both repo paths. Produces a detailed gap report showing missing tests, broken tests, and quality assessment.
+
+## Usage
+
+/qa-gap --dev-repo <path> --qa-repo <path>
+
+- --dev-repo: path to the developer repository (required)
+- --qa-repo: path to the existing QA repository (required)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- testing pyramid, test spec rules, quality gates.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-gap.md` end-to-end.
+Preserve all workflow gates (both-repo scanning, gap metrics).
+
+$ARGUMENTS

package/.claude/commands/qa-map.md

@@ -1,47 +1,47 @@
-# QA Codebase Map & Analysis
-
-Deep-scan a codebase for QA-relevant information and produce a complete analysis. Runs codebase mapping (4 parallel agents) followed by repository analysis. One command to fully understand a codebase before writing tests.
-
-## Usage
-
-/qa-map [--focus <area>] [--dev-repo <path>] [--qa-repo <path>]
-
-- No arguments: runs full map + analysis on current directory
-- --focus: run a single map area only, skip analysis (testability, risk, patterns, existing-tests)
-- --dev-repo: explicit path to developer repository
-- --qa-repo: path to existing QA repository (produces gap analysis instead of blueprint)
-
-## What It Produces
-
-### Stage 1: Codebase Map (4 parallel agents)
-- TESTABILITY.md + TEST_SURFACE.md — what's testable, entry points, mocking needs
-- RISK_MAP.md + CRITICAL_PATHS.md — business-critical paths, error handling gaps
-- CODE_PATTERNS.md + API_CONTRACTS.md — naming conventions, API shapes, auth patterns
-- TEST_ASSESSMENT.md + COVERAGE_GAPS.md — existing test quality, what's missing
-
-### Stage 2: Repository Analysis
-- SCAN_MANIFEST.md — file tree, framework detection, testable surfaces
-- QA_ANALYSIS.md — architecture overview, risk assessment, top 10 unit targets, testing pyramid
-- TEST_INVENTORY.md — every test case with ID, target, inputs, expected outcome, priority
-- QA_REPO_BLUEPRINT.md (no QA repo) or GAP_ANALYSIS.md (QA repo provided)
-
-## Instructions
-
-1. Read `CLAUDE.md` — QA standards.
-2. Create output directory: `.qa-output/codebase/`
-3. If no --focus flag, spawn 4 agents in parallel (one per focus area):
-
-For each focus area, spawn:
-
-Agent(
-  prompt="Analyze this codebase for QA purposes. Focus area: {focus}. Write documents to .qa-output/codebase/. Follow the process in your agent definition.",
-  subagent_type="general-purpose",
-  execution_context="@agents/qaa-codebase-mapper.md"
-)
-
-4. If --focus flag, spawn only that one area and stop (skip analysis stage).
-5. When all map agents complete, print summary of codebase documents produced.
-6. Run the analysis stage — execute the workflow defined in `@workflows/qa-analyze.md` end-to-end. Pass --dev-repo and --qa-repo arguments if provided. Preserve all workflow gates (scan verification, artifact checks).
-7. Print final summary: all documents produced across both stages.
-
-$ARGUMENTS
+# QA Codebase Map & Analysis
+
+Deep-scan a codebase for QA-relevant information and produce a complete analysis. Runs codebase mapping (4 parallel agents) followed by repository analysis. One command to fully understand a codebase before writing tests.
+
+## Usage
+
+/qa-map [--focus <area>] [--dev-repo <path>] [--qa-repo <path>]
+
+- No arguments: runs full map + analysis on current directory
+- --focus: run a single map area only, skip analysis (testability, risk, patterns, existing-tests)
+- --dev-repo: explicit path to developer repository
+- --qa-repo: path to existing QA repository (produces gap analysis instead of blueprint)
+
+## What It Produces
+
+### Stage 1: Codebase Map (4 parallel agents)
+- TESTABILITY.md + TEST_SURFACE.md — what's testable, entry points, mocking needs
+- RISK_MAP.md + CRITICAL_PATHS.md — business-critical paths, error handling gaps
+- CODE_PATTERNS.md + API_CONTRACTS.md — naming conventions, API shapes, auth patterns
+- TEST_ASSESSMENT.md + COVERAGE_GAPS.md — existing test quality, what's missing
+
+### Stage 2: Repository Analysis
+- SCAN_MANIFEST.md — file tree, framework detection, testable surfaces
+- QA_ANALYSIS.md — architecture overview, risk assessment, top 10 unit targets, testing pyramid
+- TEST_INVENTORY.md — every test case with ID, target, inputs, expected outcome, priority
+- QA_REPO_BLUEPRINT.md (no QA repo) or GAP_ANALYSIS.md (QA repo provided)
+
+## Instructions
+
+1. Read `CLAUDE.md` — QA standards.
+2. Create output directory: `.qa-output/codebase/`
+3. If no --focus flag, spawn 4 agents in parallel (one per focus area):
+
+For each focus area, spawn:
+
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: {focus}. Write documents to .qa-output/codebase/. Follow the process in your agent definition.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+
+4. If --focus flag, spawn only that one area and stop (skip analysis stage).
+5. When all map agents complete, print summary of codebase documents produced.
+6. Run the analysis stage — execute the workflow defined in `@workflows/qa-analyze.md` end-to-end. Pass --dev-repo and --qa-repo arguments if provided. Preserve all workflow gates (scan verification, artifact checks).
+7. Print final summary: all documents produced across both stages.
+
+$ARGUMENTS

package/.claude/commands/qa-pom.md

@@ -1,36 +1,36 @@
-# Generate Page Object Models
-
-Create or update Page Object Model files following CLAUDE.md POM rules. Checks for existing BasePage before creating one. Generates feature-specific POMs with Tier 1 locators, no assertions, and fluent action chaining.
-
-## Usage
-
-/qa-pom <path-to-pages> [--framework <name>]
-
-- path-to-pages: directory containing page/view source files or URLs to model
-- --framework: override framework auto-detection (playwright, cypress, selenium)
-
-## What It Produces
-
-- BasePage file (if not already present)
-- Feature-specific POM files following `[PageName]Page.[ext]` naming convention
-
-## Instructions
-
-1. Read `CLAUDE.md` -- POM rules, locator tier hierarchy, naming conventions.
-2. Invoke executor agent in POM-only mode:
-
-Task(
-  prompt="
-    <objective>Generate Page Object Models following CLAUDE.md POM rules</objective>
-    <execution_context>@agents/qaa-executor.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: pom-only
-    </parameters>
-  "
-)
-
-$ARGUMENTS
+# Generate Page Object Models
+
+Create or update Page Object Model files following CLAUDE.md POM rules. Checks for existing BasePage before creating one. Generates feature-specific POMs with Tier 1 locators, no assertions, and fluent action chaining.
+
+## Usage
+
+/qa-pom <path-to-pages> [--framework <name>]
+
+- path-to-pages: directory containing page/view source files or URLs to model
+- --framework: override framework auto-detection (playwright, cypress, selenium)
+
+## What It Produces
+
+- BasePage file (if not already present)
+- Feature-specific POM files following `[PageName]Page.[ext]` naming convention
+
+## Instructions
+
+1. Read `CLAUDE.md` -- POM rules, locator tier hierarchy, naming conventions.
+2. Invoke executor agent in POM-only mode:
+
+Task(
+  prompt="
+    <objective>Generate Page Object Models following CLAUDE.md POM rules</objective>
+    <execution_context>@agents/qaa-executor.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: pom-only
+    </parameters>
+  "
+)
+
+$ARGUMENTS

package/.claude/commands/qa-pr.md

@@ -1,23 +1,23 @@
-# Create QA Pull Request
-
-Create a draft PR from QA artifacts already on disk. Auto-detects git platform (GitHub, Azure DevOps, GitLab), applies your team's branch naming convention, and creates a draft PR with a summary. Asks for your branch pattern the first time and remembers it.
-
-## Usage
-
-/qa-pr [--ticket <id>] [--title <description>] [--scope <type>] [--files <glob>] [--base <branch>]
-
-- --ticket: ticket/issue ID for branch name (e.g., PROJ-123)
-- --title: short description for branch and PR title (e.g., "login tests")
-- --scope: limit to file type: unit, api, e2e, all (default: all)
-- --files: explicit file glob to include (e.g., "tests/unit/auth*")
-- --base: target branch for PR (default: auto-detect)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- git workflow, commit conventions.
-2. Execute the workflow:
-
-Follow the workflow defined in `@workflows/qa-pr.md` end-to-end.
-Preserve all workflow gates (platform detection, user confirmation before push, branch convention save).
-
-$ARGUMENTS
+# Create QA Pull Request
+
+Create a draft PR from QA artifacts already on disk. Auto-detects git platform (GitHub, Azure DevOps, GitLab), applies your team's branch naming convention, and creates a draft PR with a summary. Asks for your branch pattern the first time and remembers it.
+
+## Usage
+
+/qa-pr [--ticket <id>] [--title <description>] [--scope <type>] [--files <glob>] [--base <branch>]
+
+- --ticket: ticket/issue ID for branch name (e.g., PROJ-123)
+- --title: short description for branch and PR title (e.g., "login tests")
+- --scope: limit to file type: unit, api, e2e, all (default: all)
+- --files: explicit file glob to include (e.g., "tests/unit/auth*")
+- --base: target branch for PR (default: auto-detect)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- git workflow, commit conventions.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-pr.md` end-to-end.
+Preserve all workflow gates (platform detection, user confirmation before push, branch convention save).
+
+$ARGUMENTS

package/.claude/commands/qa-pyramid.md

@@ -1,37 +1,37 @@
-# Testing Pyramid Analysis
-
-Analyze a project's test distribution against the ideal testing pyramid from CLAUDE.md. Compares actual percentages to targets and produces an action plan to reach the recommended distribution.
-
-## Usage
-
-/qa-pyramid <path-to-tests> [--dev-repo <path>]
-
-- path-to-tests: directory containing test files
-- --dev-repo: path to developer repository (for architecture-aware target adjustment)
-
-## What It Produces
-
-- PYRAMID_ANALYSIS.md -- current vs target distribution, gap table, prioritized action plan
-
-## Instructions
-
-1. Read `CLAUDE.md` -- testing pyramid target percentages.
-2. Invoke analyzer agent for pyramid analysis:
-
-Task(
-  prompt="
-    <objective>Produce PYRAMID_ANALYSIS.md comparing actual test distribution to target pyramid</objective>
-    <execution_context>@agents/qaa-analyzer.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: pyramid-analysis
-    </parameters>
-  "
-)
-
-3. Present analysis with action plan to user.
-
-$ARGUMENTS
+# Testing Pyramid Analysis
+
+Analyze a project's test distribution against the ideal testing pyramid from CLAUDE.md. Compares actual percentages to targets and produces an action plan to reach the recommended distribution.
+
+## Usage
+
+/qa-pyramid <path-to-tests> [--dev-repo <path>]
+
+- path-to-tests: directory containing test files
+- --dev-repo: path to developer repository (for architecture-aware target adjustment)
+
+## What It Produces
+
+- PYRAMID_ANALYSIS.md -- current vs target distribution, gap table, prioritized action plan
+
+## Instructions
+
+1. Read `CLAUDE.md` -- testing pyramid target percentages.
+2. Invoke analyzer agent for pyramid analysis:
+
+Task(
+  prompt="
+    <objective>Produce PYRAMID_ANALYSIS.md comparing actual test distribution to target pyramid</objective>
+    <execution_context>@agents/qaa-analyzer.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: pyramid-analysis
+    </parameters>
+  "
+)
+
+3. Present analysis with action plan to user.
+
+$ARGUMENTS

package/.claude/commands/qa-report.md

@@ -1,38 +1,38 @@
-# QA Status Report
-
-Generate a summary report of current QA status for a project. Adapts detail level to audience: team (file-level details), management (high-level metrics), or client (coverage summary).
-
-## Usage
-
-/qa-report <path-to-tests> [--dev-repo <path>] [--audience <team|management|client>]
-
-- path-to-tests: directory containing test files
-- --dev-repo: path to developer repository (for coverage calculation)
-- --audience: report detail level (default: team)
-
-## What It Produces
-
-- QA_STATUS_REPORT.md -- metrics, testing pyramid distribution, risk areas, recommendations
-
-## Instructions
-
-1. Read `CLAUDE.md` -- testing pyramid targets, quality gates.
-2. Invoke analyzer agent for status reporting:
-
-Task(
-  prompt="
-    <objective>Produce QA_STATUS_REPORT.md with current test suite metrics and coverage</objective>
-    <execution_context>@agents/qaa-analyzer.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: status-report
-    </parameters>
-  "
-)
-
-3. Present report to user.
-
-$ARGUMENTS
+# QA Status Report
+
+Generate a summary report of current QA status for a project. Adapts detail level to audience: team (file-level details), management (high-level metrics), or client (coverage summary).
+
+## Usage
+
+/qa-report <path-to-tests> [--dev-repo <path>] [--audience <team|management|client>]
+
+- path-to-tests: directory containing test files
+- --dev-repo: path to developer repository (for coverage calculation)
+- --audience: report detail level (default: team)
+
+## What It Produces
+
+- QA_STATUS_REPORT.md -- metrics, testing pyramid distribution, risk areas, recommendations
+
+## Instructions
+
+1. Read `CLAUDE.md` -- testing pyramid targets, quality gates.
+2. Invoke analyzer agent for status reporting:
+
+Task(
+  prompt="
+    <objective>Produce QA_STATUS_REPORT.md with current test suite metrics and coverage</objective>
+    <execution_context>@agents/qaa-analyzer.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: status-report
+    </parameters>
+  "
+)
+
+3. Present report to user.
+
+$ARGUMENTS

package/.claude/commands/qa-research.md

@@ -1,33 +1,33 @@
-# QA Research
-
-Research the best testing approach for a project's stack. Investigates framework capabilities, best practices, and testing patterns using official docs and community sources.
-
-## Usage
-
-/qa-research [--mode <mode>]
-
-- No arguments: auto-detects stack and researches testing approach
-- --mode: specific research mode (stack-testing, framework-deep-dive, api-testing, e2e-strategy)
-
-## What It Produces
-
-- TESTING_STACK.md — recommended test framework, assertion libraries, mock strategies
-- FRAMEWORK_CAPABILITIES.md — deep dive into detected test framework
-- API_TESTING_STRATEGY.md — endpoint testing patterns for this stack
-- E2E_STRATEGY.md — E2E approach for the frontend (if detected)
-
-## Instructions
-
-1. Read `CLAUDE.md` — QA standards.
-2. Detect project stack from package.json, requirements.txt, or similar.
-3. Spawn researcher agent:
-
-Agent(
-  prompt="Research the testing ecosystem for this project. Mode: {mode}. Write findings to .qa-output/research/. Follow the process in your agent definition.",
-  subagent_type="general-purpose",
-  execution_context="@agents/qaa-project-researcher.md"
-)
-
-4. Present findings with confidence levels.
-
-$ARGUMENTS
+# QA Research
+
+Research the best testing approach for a project's stack. Investigates framework capabilities, best practices, and testing patterns using official docs and community sources.
+
+## Usage
+
+/qa-research [--mode <mode>]
+
+- No arguments: auto-detects stack and researches testing approach
+- --mode: specific research mode (stack-testing, framework-deep-dive, api-testing, e2e-strategy)
+
+## What It Produces
+
+- TESTING_STACK.md — recommended test framework, assertion libraries, mock strategies
+- FRAMEWORK_CAPABILITIES.md — deep dive into detected test framework
+- API_TESTING_STRATEGY.md — endpoint testing patterns for this stack
+- E2E_STRATEGY.md — E2E approach for the frontend (if detected)
+
+## Instructions
+
+1. Read `CLAUDE.md` — QA standards.
+2. Detect project stack from package.json, requirements.txt, or similar.
+3. Spawn researcher agent:
+
+Agent(
+  prompt="Research the testing ecosystem for this project. Mode: {mode}. Write findings to .qa-output/research/. Follow the process in your agent definition.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-project-researcher.md"
+)
+
+4. Present findings with confidence levels.
+
+$ARGUMENTS

package/.claude/commands/qa-start.md

@@ -1,22 +1,22 @@
-# QA Automation -- Full Pipeline
-
-Run the complete QA automation pipeline. Analyzes a repository, generates a standards-compliant test suite, validates it, and delivers everything as a draft PR.
-
-## Usage
-
-/qa-start [--dev-repo <path>] [--qa-repo <path>] [--auto]
-
-- No arguments: uses current directory as dev repo (Option 1)
-- --dev-repo: explicit path to developer repository
-- --qa-repo: path to existing QA repository (triggers Option 2 or 3)
-- --auto: enable auto-advance mode (no pauses at safe checkpoints)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- all QA standards that govern the pipeline.
-2. Execute the workflow:
-
-Follow the workflow defined in `@workflows/qa-start.md` end-to-end.
-Preserve all workflow gates (stage transitions, checkpoints, error handling, state updates, commits).
-
-$ARGUMENTS
+# QA Automation -- Full Pipeline
+
+Run the complete QA automation pipeline. Analyzes a repository, generates a standards-compliant test suite, validates it, and delivers everything as a draft PR.
+
+## Usage
+
+/qa-start [--dev-repo <path>] [--qa-repo <path>] [--auto]
+
+- No arguments: uses current directory as dev repo (Option 1)
+- --dev-repo: explicit path to developer repository
+- --qa-repo: path to existing QA repository (triggers Option 2 or 3)
+- --auto: enable auto-advance mode (no pauses at safe checkpoints)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- all QA standards that govern the pipeline.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-start.md` end-to-end.
+Preserve all workflow gates (stage transitions, checkpoints, error handling, state updates, commits).
+
+$ARGUMENTS

package/.claude/commands/qa-testid.md

@@ -1,19 +1,19 @@
-# Inject Test IDs
-
-Scan frontend source code, audit missing data-testid attributes, and inject them following the naming convention in CLAUDE.md. Creates a separate branch for the changes.
-
-## Usage
-
-/qa-testid [<source-directory>]
-
-- source-directory: path to frontend source (auto-detects if omitted)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- data-testid Convention section.
-2. Execute the workflow:
-
-Follow the workflow defined in `@workflows/qa-testid.md` end-to-end.
-Preserve all workflow gates (framework detection, user approval, branch creation).
-
-$ARGUMENTS
+# Inject Test IDs
+
+Scan frontend source code, audit missing data-testid attributes, and inject them following the naming convention in CLAUDE.md. Creates a separate branch for the changes.
+
+## Usage
+
+/qa-testid [<source-directory>]
+
+- source-directory: path to frontend source (auto-detects if omitted)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- data-testid Convention section.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-testid.md` end-to-end.
+Preserve all workflow gates (framework detection, user approval, branch creation).
+
+$ARGUMENTS

package/.claude/commands/qa-validate.md

@@ -1,42 +1,42 @@
-# QA Test Validation
-
-Validate existing test files against CLAUDE.md standards. Runs 4-layer static validation (syntax, structure, dependencies, logic) and optionally executes E2E tests against a live app to verify locators and assertions with real page data.
-
-## Usage
-
-/qa-validate [<test-directory>] [--classify] [--run --app-url <url>]
-
-- test-directory: path to test files (auto-detects if omitted)
-- --classify: also run bug-detective to classify failures
-- --run: execute E2E tests against a live application after static validation
-- --app-url: URL of running application (auto-detects if not provided)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- quality gates, locator tiers, assertion rules.
-2. Execute the static validation workflow:
-
-Follow the workflow defined in `@workflows/qa-validate.md` end-to-end.
-Preserve all workflow gates (fix loops, classification).
-
-3. If `--run` flag is present and E2E test files exist in the validated directory, invoke the E2E runner:
-
-Task(
-  prompt="
-    <objective>Run E2E tests against live application, capture real locators, fix mismatches, loop until pass</objective>
-    <execution_context>@agents/qaa-e2e-runner.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - {E2E test files from validated directory}
-    - {POM files from validated directory}
-    </files_to_read>
-    <parameters>
-    app_url: {from --app-url flag or auto-detect}
-    output_dir: .qa-output
-    </parameters>
-  "
-)
-
-4. Present combined results: static validation + E2E execution (if ran).
-
-$ARGUMENTS
+# QA Test Validation
+
+Validate existing test files against CLAUDE.md standards. Runs 4-layer static validation (syntax, structure, dependencies, logic) and optionally executes E2E tests against a live app to verify locators and assertions with real page data.
+
+## Usage
+
+/qa-validate [<test-directory>] [--classify] [--run --app-url <url>]
+
+- test-directory: path to test files (auto-detects if omitted)
+- --classify: also run bug-detective to classify failures
+- --run: execute E2E tests against a live application after static validation
+- --app-url: URL of running application (auto-detects if not provided)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- quality gates, locator tiers, assertion rules.
+2. Execute the static validation workflow:
+
+Follow the workflow defined in `@workflows/qa-validate.md` end-to-end.
+Preserve all workflow gates (fix loops, classification).
+
+3. If `--run` flag is present and E2E test files exist in the validated directory, invoke the E2E runner:
+
+Task(
+  prompt="
+    <objective>Run E2E tests against live application, capture real locators, fix mismatches, loop until pass</objective>
+    <execution_context>@agents/qaa-e2e-runner.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    - {E2E test files from validated directory}
+    - {POM files from validated directory}
+    </files_to_read>
+    <parameters>
+    app_url: {from --app-url flag or auto-detect}
+    output_dir: .qa-output
+    </parameters>
+  "
+)
+
+4. Present combined results: static validation + E2E execution (if ran).
+
+$ARGUMENTS