qaa-agent 1.6.2 → 1.6.3

package/docs/COMMANDS.md

@@ -1,341 +1,341 @@
-# QAA Commands Reference
-
-## When to Use What
-
-```
-"I have a project with no tests"                    → /qa-start
-"I want to understand the codebase first"            → /qa-map
-"I need tests for a specific feature"                → /create-test
-"I have a Jira/Linear ticket to cover"               → /qa-from-ticket
-"I want to check if my tests are good"               → /qa-validate
-"My tests are failing after a deploy"                → /qa-fix
-"I want to ship my tests as a PR"                    → /qa-pr
-"I want a full report for my manager"                → /qa-report
-"I need to know what's missing in our test suite"    → /qa-gap
-"I want to add data-testid to components"            → /qa-testid
-"I need Page Object Models"                          → /qa-pom
-"I want to audit test quality"                       → /qa-audit
-"I need a QA repo structure from scratch"            → /qa-blueprint
-"I want to see our testing pyramid balance"          → /qa-pyramid
-"I want to analyze without generating anything"      → /qa-analyze
-"I want to research best testing practices"          → /qa-research
-"I want to improve existing tests"                   → /update-test
-```
-
----
-
-## Full Pipeline
-
-### /qa-start
-
-**What it does:** Runs the entire QA automation pipeline end-to-end. Scans the repo, maps the codebase, analyzes architecture, plans test cases, generates test files, validates them, runs E2E tests against the live app, and delivers everything as a draft PR.
-
-**When to use:** Starting QA from scratch on a project, or doing a full gap-fill on an existing QA repo.
-
-```
-/qa-start --dev-repo /path/to/project
-/qa-start --dev-repo /path/to/project --qa-repo /path/to/tests
-/qa-start --dev-repo /path/to/project --auto
-```
-
-**Pipeline:**
-```
-scan → map → analyze → [testid-inject] → plan → generate → validate → [e2e-run] → [bug-detective] → deliver
-```
-
-**Produces:** SCAN_MANIFEST.md, 8 codebase map documents, QA_ANALYSIS.md, TEST_INVENTORY.md, QA_REPO_BLUEPRINT.md, test files, POMs, fixtures, VALIDATION_REPORT.md, E2E_RUN_REPORT.md, draft PR.
-
----
-
-## Discovery & Analysis
-
-### /qa-map
-
-**What it does:** Deep-scans the codebase with 4 parallel agents (testability, risk, patterns, existing tests) and produces 8 documents that become the shared context for all other commands. This is the "brain" of the system.
-
-**When to use:** Before using `/create-test` on a mature project. Run it once, and every subsequent command benefits from the codebase knowledge.
-
-```
-/qa-map
-/qa-map --focus testability
-/qa-map --focus risk
-```
-
-**Produces:** TESTABILITY.md, TEST_SURFACE.md, RISK_MAP.md, CRITICAL_PATHS.md, CODE_PATTERNS.md, API_CONTRACTS.md, TEST_ASSESSMENT.md, COVERAGE_GAPS.md — all in `.qa-output/codebase/`.
-
----
-
-### /qa-analyze
-
-**What it does:** Scans and analyzes a repository without generating any tests. Produces assessment documents only — architecture overview, risk areas, test inventory with every test case specified, and a testing pyramid recommendation.
-
-**When to use:** You want to understand what needs testing before committing to generation. Good for presenting a plan to the team before executing.
-
-```
-/qa-analyze
-/qa-analyze --dev-repo /path/to/project
-/qa-analyze --dev-repo /path/to/project --qa-repo /path/to/tests
-```
-
-**Produces:** SCAN_MANIFEST.md, QA_ANALYSIS.md, TEST_INVENTORY.md, and either QA_REPO_BLUEPRINT.md (no QA repo) or GAP_ANALYSIS.md (QA repo provided).
-
----
-
-### /qa-research
-
-**What it does:** Researches the best testing stack, frameworks, and patterns for a specific project. Checks official docs, community best practices, and produces opinionated recommendations with confidence levels.
-
-**When to use:** You're setting up testing for the first time and want to know which framework to use, or you're evaluating whether to switch from Jest to Vitest.
-
-```
-/qa-research
-/qa-research --focus api-testing
-/qa-research --focus e2e-strategy
-```
-
-**Produces:** TESTING_STACK.md, FRAMEWORK_CAPABILITIES.md, API_TESTING_STRATEGY.md, E2E_STRATEGY.md (depending on mode).
-
----
-
-### /qa-gap
-
-**What it does:** Compares a dev repo against its QA repo to find coverage gaps. Shows what's tested, what's missing, what's broken, and what's low quality.
-
-**When to use:** You already have tests but suspect there are holes. Want a concrete list of what to add next.
-
-```
-/qa-gap --dev-repo /path/to/project --qa-repo /path/to/tests
-```
-
-**Produces:** GAP_ANALYSIS.md with coverage map, missing tests, broken tests, and prioritized recommendations.
-
----
-
-### /qa-pyramid
-
-**What it does:** Analyzes the distribution of your test suite against the ideal testing pyramid (60-70% unit, 10-15% integration, 20-25% API, 3-5% E2E). Shows where you're heavy and where you're light.
-
-**When to use:** You want to know if your test suite is balanced or if you're over-invested in E2E and under-invested in unit tests.
-
-```
-/qa-pyramid ./tests
-/qa-pyramid ./tests --dev-repo /path/to/project
-```
-
-**Produces:** PYRAMID_ANALYSIS.md with current vs target distribution and an action plan.
-
----
-
-## Test Creation
-
-### /create-test
-
-**What it does:** Generates tests for a specific feature or module. Reads the codebase map (if available) to understand the project's code patterns, API contracts, and existing conventions. If E2E tests are generated and an app is running, opens a real browser, captures actual locators from the page, fixes any mismatches, and loops until tests pass.
-
-**When to use:** Daily work. A new feature shipped and you need tests for it.
-
-```
-/create-test login
-/create-test "checkout flow"
-/create-test "user API" --dev-repo /path/to/project
-/create-test login --app-url http://localhost:3000
-/create-test login --skip-run
-```
-
-**Produces:** Test spec files, POMs, fixtures. E2E_RUN_REPORT.md if tests were run against the app.
-
----
-
-### /qa-from-ticket
-
-**What it does:** Fetches a ticket from Jira, Linear, GitHub Issues, or a file. Extracts acceptance criteria and edge cases. Maps each criterion to test cases with a traceability matrix. Generates test files and validates them.
-
-**When to use:** You work from tickets and want every acceptance criterion to have a corresponding test before the feature ships.
-
-```
-/qa-from-ticket https://company.atlassian.net/browse/PROJ-123
-/qa-from-ticket #456
-/qa-from-ticket ./tickets/feature-spec.md
-/qa-from-ticket "As a user I want to reset my password via email"
-```
-
-**Produces:** TEST_CASES_FROM_TICKET.md (traceability matrix), GENERATION_PLAN_TICKET.md, test files, VALIDATION_REPORT.md.
-
----
-
-### /qa-pom
-
-**What it does:** Generates Page Object Model files for given pages. Follows CLAUDE.md POM rules: one class per page, no assertions, locators as properties, extends shared base.
-
-**When to use:** You have pages that need POMs but don't want to generate full test suites yet.
-
-```
-/qa-pom ./src/pages
-/qa-pom ./src/pages --framework playwright
-```
-
-**Produces:** POM files in `pages/` directory with BasePage and feature pages.
-
----
-
-### /qa-testid
-
-**What it does:** Scans frontend source code, audits interactive elements for missing `data-testid` attributes, and injects them following the naming convention (`{context}-{description}-{element-type}` in kebab-case). Creates a separate branch for the changes.
-
-**When to use:** Before writing E2E tests. You want every button, input, and link to have a stable test ID.
-
-```
-/qa-testid ./src/components
-/qa-testid ./src
-```
-
-**Produces:** TESTID_AUDIT_REPORT.md (coverage score, proposed values) and modified source files with `data-testid` attributes.
-
----
-
-## Validation & Fixing
-
-### /qa-validate
-
-**What it does:** Validates test files against CLAUDE.md standards. Runs 4 static layers (syntax, structure, dependencies, logic) with auto-fix up to 3 loops. Optionally runs E2E tests against a live app to verify locators and assertions with real page data.
-
-**When to use:** After writing or generating tests, before shipping. Or as a quality check on an existing test suite.
-
-```
-/qa-validate ./tests
-/qa-validate ./tests --classify
-/qa-validate ./tests --run --app-url http://localhost:3000
-```
-
-**Produces:** VALIDATION_REPORT.md. FAILURE_CLASSIFICATION_REPORT.md if `--classify` used. E2E_RUN_REPORT.md if `--run` used.
-
----
-
-### /qa-fix
-
-**What it does:** Diagnoses and fixes broken test files. Reads failing tests, runs them, classifies each failure (app bug vs test code error vs environment issue), and auto-fixes test code errors.
-
-**When to use:** Tests that were passing started failing after a deploy or code change.
-
-```
-/qa-fix ./tests/e2e/checkout*
-/qa-fix ./tests --error "timeout waiting for selector"
-```
-
-**Produces:** Fixed test files. FAILURE_CLASSIFICATION_REPORT.md with evidence for each failure.
-
----
-
-### /update-test
-
-**What it does:** Improves existing tests without rewriting them. Upgrades locator tiers, makes assertions more specific, fixes naming conventions, adds missing test IDs.
-
-**When to use:** Your tests work but don't follow current standards. You want incremental improvement, not a rewrite.
-
-```
-/update-test ./tests
-/update-test ./tests --scope locators
-/update-test ./tests --scope assertions
-```
-
-**Produces:** Updated test files with improvements applied.
-
----
-
-## Reporting & Auditing
-
-### /qa-audit
-
-**What it does:** Full 6-dimension quality audit of a test suite. Scores: Locator Quality (20%), Assertion Specificity (20%), POM Compliance (15%), Test Coverage (20%), Naming Convention (15%), Test Data Management (10%). Gives a weighted overall score.
-
-**When to use:** You want a quality score for your test suite with concrete recommendations for improvement.
-
-```
-/qa-audit ./tests
-/qa-audit ./tests --dev-repo /path/to/project
-```
-
-**Produces:** QA_AUDIT_REPORT.md with scores, critical issues, and effort-estimated recommendations (S/M/L).
-
----
-
-### /qa-report
-
-**What it does:** Generates a QA status report adapted to the audience. Team level gets file-level details. Management gets high-level metrics. Client gets a coverage summary.
-
-**When to use:** Standups, sprint reviews, client updates.
-
-```
-/qa-report ./tests
-/qa-report ./tests --audience management
-/qa-report ./tests --audience client
-```
-
-**Produces:** QA_STATUS_REPORT.md with metrics, pyramid distribution, risk areas, recommendations.
-
----
-
-### /qa-blueprint
-
-**What it does:** Generates a complete QA repository structure blueprint — recommended stack, folder layout, config files, CI/CD pipeline, npm scripts, and definition of done.
-
-**When to use:** You're starting a QA repo from scratch and want a solid structure before writing the first test.
-
-```
-/qa-blueprint
-/qa-blueprint --dev-repo /path/to/project
-```
-
-**Produces:** SCAN_MANIFEST.md, QA_REPO_BLUEPRINT.md.
-
----
-
-## Delivery
-
-### /qa-pr
-
-**What it does:** Creates a draft PR from QA artifacts already on disk. Auto-detects git platform (GitHub, Azure DevOps, GitLab). Applies your team's branch naming convention (asks once, remembers forever). Shows what will be committed and waits for your confirmation before pushing.
-
-**When to use:** After generating or fixing tests, you want to package them as a PR.
-
-```
-/qa-pr --ticket PROJ-123 --title "login tests"
-/qa-pr --scope e2e
-/qa-pr --ticket PROJ-456 --title "checkout" --base develop
-```
-
-**Produces:** Git branch (following your convention), commits, draft PR with summary. Returns the PR URL.
-
----
-
-## Common Flows
-
-### New project, no tests
-```
-/qa-start --dev-repo ./myproject --auto
-```
-
-### Mature project, new feature
-```
-/qa-map                                    # once
-/create-test "password reset"              # generates + runs
-/qa-pr --ticket PROJ-123 "reset tests"     # ships as PR
-```
-
-### From a Jira ticket
-```
-/qa-from-ticket https://jira.company.com/browse/PROJ-456
-/qa-pr --ticket PROJ-456 "login flow"
-```
-
-### Fix broken tests after deploy
-```
-/qa-fix ./tests/e2e/checkout*
-/qa-pr --ticket PROJ-789 "fix checkout tests"
-```
-
-### Quality check before release
-```
-/qa-audit ./tests --dev-repo ./myproject
-/qa-report ./tests --audience management
-```
+# QAA Commands Reference
+
+## When to Use What
+
+```
+"I have a project with no tests"                    → /qa-start
+"I want to understand the codebase first"            → /qa-map
+"I need tests for a specific feature"                → /create-test
+"I have a Jira/Linear ticket to cover"               → /qa-from-ticket
+"I want to check if my tests are good"               → /qa-validate
+"My tests are failing after a deploy"                → /qa-fix
+"I want to ship my tests as a PR"                    → /qa-pr
+"I want a full report for my manager"                → /qa-report
+"I need to know what's missing in our test suite"    → /qa-gap
+"I want to add data-testid to components"            → /qa-testid
+"I need Page Object Models"                          → /qa-pom
+"I want to audit test quality"                       → /qa-audit
+"I need a QA repo structure from scratch"            → /qa-blueprint
+"I want to see our testing pyramid balance"          → /qa-pyramid
+"I want to analyze without generating anything"      → /qa-analyze
+"I want to research best testing practices"          → /qa-research
+"I want to improve existing tests"                   → /update-test
+```
+
+---
+
+## Full Pipeline
+
+### /qa-start
+
+**What it does:** Runs the entire QA automation pipeline end-to-end. Scans the repo, maps the codebase, analyzes architecture, plans test cases, generates test files, validates them, runs E2E tests against the live app, and delivers everything as a draft PR.
+
+**When to use:** Starting QA from scratch on a project, or doing a full gap-fill on an existing QA repo.
+
+```
+/qa-start --dev-repo /path/to/project
+/qa-start --dev-repo /path/to/project --qa-repo /path/to/tests
+/qa-start --dev-repo /path/to/project --auto
+```
+
+**Pipeline:**
+```
+scan → map → analyze → [testid-inject] → plan → generate → validate → [e2e-run] → [bug-detective] → deliver
+```
+
+**Produces:** SCAN_MANIFEST.md, 8 codebase map documents, QA_ANALYSIS.md, TEST_INVENTORY.md, QA_REPO_BLUEPRINT.md, test files, POMs, fixtures, VALIDATION_REPORT.md, E2E_RUN_REPORT.md, draft PR.
+
+---
+
+## Discovery & Analysis
+
+### /qa-map
+
+**What it does:** Deep-scans the codebase with 4 parallel agents (testability, risk, patterns, existing tests) and produces 8 documents that become the shared context for all other commands. This is the "brain" of the system.
+
+**When to use:** Before using `/create-test` on a mature project. Run it once, and every subsequent command benefits from the codebase knowledge.
+
+```
+/qa-map
+/qa-map --focus testability
+/qa-map --focus risk
+```
+
+**Produces:** TESTABILITY.md, TEST_SURFACE.md, RISK_MAP.md, CRITICAL_PATHS.md, CODE_PATTERNS.md, API_CONTRACTS.md, TEST_ASSESSMENT.md, COVERAGE_GAPS.md — all in `.qa-output/codebase/`.
+
+---
+
+### /qa-analyze
+
+**What it does:** Scans and analyzes a repository without generating any tests. Produces assessment documents only — architecture overview, risk areas, test inventory with every test case specified, and a testing pyramid recommendation.
+
+**When to use:** You want to understand what needs testing before committing to generation. Good for presenting a plan to the team before executing.
+
+```
+/qa-analyze
+/qa-analyze --dev-repo /path/to/project
+/qa-analyze --dev-repo /path/to/project --qa-repo /path/to/tests
+```
+
+**Produces:** SCAN_MANIFEST.md, QA_ANALYSIS.md, TEST_INVENTORY.md, and either QA_REPO_BLUEPRINT.md (no QA repo) or GAP_ANALYSIS.md (QA repo provided).
+
+---
+
+### /qa-research
+
+**What it does:** Researches the best testing stack, frameworks, and patterns for a specific project. Checks official docs, community best practices, and produces opinionated recommendations with confidence levels.
+
+**When to use:** You're setting up testing for the first time and want to know which framework to use, or you're evaluating whether to switch from Jest to Vitest.
+
+```
+/qa-research
+/qa-research --focus api-testing
+/qa-research --focus e2e-strategy
+```
+
+**Produces:** TESTING_STACK.md, FRAMEWORK_CAPABILITIES.md, API_TESTING_STRATEGY.md, E2E_STRATEGY.md (depending on mode).
+
+---
+
+### /qa-gap
+
+**What it does:** Compares a dev repo against its QA repo to find coverage gaps. Shows what's tested, what's missing, what's broken, and what's low quality.
+
+**When to use:** You already have tests but suspect there are holes. Want a concrete list of what to add next.
+
+```
+/qa-gap --dev-repo /path/to/project --qa-repo /path/to/tests
+```
+
+**Produces:** GAP_ANALYSIS.md with coverage map, missing tests, broken tests, and prioritized recommendations.
+
+---
+
+### /qa-pyramid
+
+**What it does:** Analyzes the distribution of your test suite against the ideal testing pyramid (60-70% unit, 10-15% integration, 20-25% API, 3-5% E2E). Shows where you're heavy and where you're light.
+
+**When to use:** You want to know if your test suite is balanced or if you're over-invested in E2E and under-invested in unit tests.
+
+```
+/qa-pyramid ./tests
+/qa-pyramid ./tests --dev-repo /path/to/project
+```
+
+**Produces:** PYRAMID_ANALYSIS.md with current vs target distribution and an action plan.
+
+---
+
+## Test Creation
+
+### /create-test
+
+**What it does:** Generates tests for a specific feature or module. Reads the codebase map (if available) to understand the project's code patterns, API contracts, and existing conventions. If E2E tests are generated and an app is running, opens a real browser, captures actual locators from the page, fixes any mismatches, and loops until tests pass.
+
+**When to use:** Daily work. A new feature shipped and you need tests for it.
+
+```
+/create-test login
+/create-test "checkout flow"
+/create-test "user API" --dev-repo /path/to/project
+/create-test login --app-url http://localhost:3000
+/create-test login --skip-run
+```
+
+**Produces:** Test spec files, POMs, fixtures. E2E_RUN_REPORT.md if tests were run against the app.
+
+---
+
+### /qa-from-ticket
+
+**What it does:** Fetches a ticket from Jira, Linear, GitHub Issues, or a file. Extracts acceptance criteria and edge cases. Maps each criterion to test cases with a traceability matrix. Generates test files and validates them.
+
+**When to use:** You work from tickets and want every acceptance criterion to have a corresponding test before the feature ships.
+
+```
+/qa-from-ticket https://company.atlassian.net/browse/PROJ-123
+/qa-from-ticket #456
+/qa-from-ticket ./tickets/feature-spec.md
+/qa-from-ticket "As a user I want to reset my password via email"
+```
+
+**Produces:** TEST_CASES_FROM_TICKET.md (traceability matrix), GENERATION_PLAN_TICKET.md, test files, VALIDATION_REPORT.md.
+
+---
+
+### /qa-pom
+
+**What it does:** Generates Page Object Model files for given pages. Follows CLAUDE.md POM rules: one class per page, no assertions, locators as properties, extends shared base.
+
+**When to use:** You have pages that need POMs but don't want to generate full test suites yet.
+
+```
+/qa-pom ./src/pages
+/qa-pom ./src/pages --framework playwright
+```
+
+**Produces:** POM files in `pages/` directory with BasePage and feature pages.
+
+---
+
+### /qa-testid
+
+**What it does:** Scans frontend source code, audits interactive elements for missing `data-testid` attributes, and injects them following the naming convention (`{context}-{description}-{element-type}` in kebab-case). Creates a separate branch for the changes.
+
+**When to use:** Before writing E2E tests. You want every button, input, and link to have a stable test ID.
+
+```
+/qa-testid ./src/components
+/qa-testid ./src
+```
+
+**Produces:** TESTID_AUDIT_REPORT.md (coverage score, proposed values) and modified source files with `data-testid` attributes.
+
+---
+
+## Validation & Fixing
+
+### /qa-validate
+
+**What it does:** Validates test files against CLAUDE.md standards. Runs 4 static layers (syntax, structure, dependencies, logic) with auto-fix up to 3 loops. Optionally runs E2E tests against a live app to verify locators and assertions with real page data.
+
+**When to use:** After writing or generating tests, before shipping. Or as a quality check on an existing test suite.
+
+```
+/qa-validate ./tests
+/qa-validate ./tests --classify
+/qa-validate ./tests --run --app-url http://localhost:3000
+```
+
+**Produces:** VALIDATION_REPORT.md. FAILURE_CLASSIFICATION_REPORT.md if `--classify` used. E2E_RUN_REPORT.md if `--run` used.
+
+---
+
+### /qa-fix
+
+**What it does:** Diagnoses and fixes broken test files. Reads failing tests, runs them, classifies each failure (app bug vs test code error vs environment issue), and auto-fixes test code errors.
+
+**When to use:** Tests that were passing started failing after a deploy or code change.
+
+```
+/qa-fix ./tests/e2e/checkout*
+/qa-fix ./tests --error "timeout waiting for selector"
+```
+
+**Produces:** Fixed test files. FAILURE_CLASSIFICATION_REPORT.md with evidence for each failure.
+
+---
+
+### /update-test
+
+**What it does:** Improves existing tests without rewriting them. Upgrades locator tiers, makes assertions more specific, fixes naming conventions, adds missing test IDs.
+
+**When to use:** Your tests work but don't follow current standards. You want incremental improvement, not a rewrite.
+
+```
+/update-test ./tests
+/update-test ./tests --scope locators
+/update-test ./tests --scope assertions
+```
+
+**Produces:** Updated test files with improvements applied.
+
+---
+
+## Reporting & Auditing
+
+### /qa-audit
+
+**What it does:** Full 6-dimension quality audit of a test suite. Scores: Locator Quality (20%), Assertion Specificity (20%), POM Compliance (15%), Test Coverage (20%), Naming Convention (15%), Test Data Management (10%). Gives a weighted overall score.
+
+**When to use:** You want a quality score for your test suite with concrete recommendations for improvement.
+
+```
+/qa-audit ./tests
+/qa-audit ./tests --dev-repo /path/to/project
+```
+
+**Produces:** QA_AUDIT_REPORT.md with scores, critical issues, and effort-estimated recommendations (S/M/L).
+
+---
+
+### /qa-report
+
+**What it does:** Generates a QA status report adapted to the audience. Team level gets file-level details. Management gets high-level metrics. Client gets a coverage summary.
+
+**When to use:** Standups, sprint reviews, client updates.
+
+```
+/qa-report ./tests
+/qa-report ./tests --audience management
+/qa-report ./tests --audience client
+```
+
+**Produces:** QA_STATUS_REPORT.md with metrics, pyramid distribution, risk areas, recommendations.
+
+---
+
+### /qa-blueprint
+
+**What it does:** Generates a complete QA repository structure blueprint — recommended stack, folder layout, config files, CI/CD pipeline, npm scripts, and definition of done.
+
+**When to use:** You're starting a QA repo from scratch and want a solid structure before writing the first test.
+
+```
+/qa-blueprint
+/qa-blueprint --dev-repo /path/to/project
+```
+
+**Produces:** SCAN_MANIFEST.md, QA_REPO_BLUEPRINT.md.
+
+---
+
+## Delivery
+
+### /qa-pr
+
+**What it does:** Creates a draft PR from QA artifacts already on disk. Auto-detects git platform (GitHub, Azure DevOps, GitLab). Applies your team's branch naming convention (asks once, remembers forever). Shows what will be committed and waits for your confirmation before pushing.
+
+**When to use:** After generating or fixing tests, you want to package them as a PR.
+
+```
+/qa-pr --ticket PROJ-123 --title "login tests"
+/qa-pr --scope e2e
+/qa-pr --ticket PROJ-456 --title "checkout" --base develop
+```
+
+**Produces:** Git branch (following your convention), commits, draft PR with summary. Returns the PR URL.
+
+---
+
+## Common Flows
+
+### New project, no tests
+```
+/qa-start --dev-repo ./myproject --auto
+```
+
+### Mature project, new feature
+```
+/qa-map                                    # once
+/create-test "password reset"              # generates + runs
+/qa-pr --ticket PROJ-123 "reset tests"     # ships as PR
+```
+
+### From a Jira ticket
+```
+/qa-from-ticket https://jira.company.com/browse/PROJ-456
+/qa-pr --ticket PROJ-456 "login flow"
+```
+
+### Fix broken tests after deploy
+```
+/qa-fix ./tests/e2e/checkout*
+/qa-pr --ticket PROJ-789 "fix checkout tests"
+```
+
+### Quality check before release
+```
+/qa-audit ./tests --dev-repo ./myproject
+/qa-report ./tests --audience management
+```