qaa-agent 1.6.1 → 1.6.3

package/.claude/commands/create-test.md

@@ -1,164 +1,164 @@
-# Create Automated Tests
-
-Generate production-ready test files with POM pattern for a specific feature or module. Reads codebase map, existing analysis artifacts, and CLAUDE.md standards to produce tests that match the project's actual code patterns. If E2E tests are generated and an app URL is available, runs them against the live app and fixes locators until they pass.
-
-## Usage
-
-/create-test <feature-name> [--dev-repo <path>] [--app-url <url>] [--skip-run]
-
-- feature-name: which feature to test (e.g., "login", "checkout", "user API")
-- --dev-repo: path to developer repository (default: current directory)
-- --app-url: URL of running application for E2E test execution (auto-detects if not provided)
-- --skip-run: skip E2E execution, only generate and statically validate
-
-## What It Produces
-
-- Test spec files (unit, API, E2E as appropriate for the feature)
-- Page Object Model files (for E2E tests)
-- Fixture files (test data)
-- E2E_RUN_REPORT.md (if E2E tests were run against live app)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- POM rules, locator tiers, assertion rules, naming conventions, quality gates.
-2. Read existing analysis artifacts if available:
-   - `.qa-output/QA_ANALYSIS.md` -- architecture context
-   - `.qa-output/TEST_INVENTORY.md` -- pre-defined test cases for this feature
-3. Read codebase map if available (check `.qa-output/codebase/`):
-   - `CODE_PATTERNS.md` -- naming conventions, import style, code patterns to match
-   - `API_CONTRACTS.md` -- request/response shapes for API tests
-   - `TEST_SURFACE.md` -- function signatures and testable entry points
-   - `TESTABILITY.md` -- pure functions vs stateful code, mock boundaries
-   If codebase map does not exist, run `/qa-map` first for best results, or proceed without it.
-
-4. **Check existing locator registry and extract new locators from live app:**
-
-   a. **Check the locator registry first.** Read `.qa-output/locators/LOCATOR_REGISTRY.md` if it exists. This is the accumulated registry of all locators previously extracted from the live app. Check if locators for this feature's pages already exist.
-
-   b. **If locators for this feature's pages are already in the registry AND no `--app-url` was provided:** Skip browser extraction -- reuse existing locators. Print: `"Reusing cached locators for {feature} from registry."`
-
-   c. **If locators are missing or `--app-url` was provided:** Use the Playwright MCP to navigate the app and extract real locators BEFORE generating tests.
-
-   **Browser extraction process:**
-
-   1. Navigate to the feature's relevant pages:
-      ```
-      mcp__playwright__browser_navigate({ url: "{app_url}/{feature_path}" })
-      ```
-
-   2. Take an accessibility snapshot of each page to discover all interactive elements:
-      ```
-      mcp__playwright__browser_snapshot()
-      ```
-
-   3. Extract real locators from the snapshot -- collect:
-      - All `data-testid` attributes present on the page
-      - ARIA roles with accessible names (buttons, inputs, links, etc.)
-      - Form labels and placeholders
-      - Navigation structure and page layout
-
-   4. If the feature has multiple pages/views (e.g., login -> dashboard), navigate through the flow:
-      ```
-      mcp__playwright__browser_fill_form({ ... })
-      mcp__playwright__browser_click({ element: "..." })
-      mcp__playwright__browser_snapshot()  // capture next page
-      ```
-
-   5. Write per-feature locator file to `.qa-output/locators/{feature}.locators.md`:
-      ```markdown
-      # Locators -- {feature}
-
-      Extracted: {date}
-      App URL: {app_url}
-
-      ## Page: {page_name} ({url})
-
-      | Element | Locator Type | Locator Value | Tier |
-      |---------|-------------|---------------|------|
-      | Email input | data-testid | login-email-input | 1 |
-      | Password input | data-testid | login-password-input | 1 |
-      | Submit button | role + name | button "Log in" | 1 |
-      | Remember me | label | "Remember me" | 2 |
-
-      ## Page: {next_page} ({url})
-      ...
-      ```
-
-   6. Update the registry `.qa-output/locators/LOCATOR_REGISTRY.md` -- merge new locators into the central index:
-      ```markdown
-      # Locator Registry
-
-      Last updated: {date}
-      Total pages: {N}
-      Total locators: {N}
-
-      ## Index
-
-      | Feature | File | Pages | Locators | Extracted |
-      |---------|------|-------|----------|-----------|
-      | login | login.locators.md | 2 | 14 | 2026-03-25 |
-      | checkout | checkout.locators.md | 3 | 22 | 2026-03-25 |
-      | dashboard | dashboard.locators.md | 1 | 8 | 2026-03-25 |
-
-      ## All Locators by Page
-
-      ### /login
-      | Element | Locator Type | Locator Value | Tier | Source |
-      |---------|-------------|---------------|------|--------|
-      | Email input | data-testid | login-email-input | 1 | login.locators.md |
-      | ... | ... | ... | ... | ... |
-
-      ### /dashboard
-      ...
-      ```
-
-   If no app URL is available and no locators exist in the registry for this feature, skip this step -- the executor will propose locators based on source code analysis and CLAUDE.md conventions.
-
-5. Invoke executor agent to generate test files:
-
-Task(
-  prompt="
-    <objective>Generate test files for the specified feature following CLAUDE.md standards, using codebase map for context</objective>
-    <execution_context>@agents/qaa-executor.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/locators/LOCATOR_REGISTRY.md (if exists -- accumulated real locators)
-    - .qa-output/locators/{feature}.locators.md (if exists -- feature-specific locators)
-    - .qa-output/codebase/CODE_PATTERNS.md (if exists)
-    - .qa-output/codebase/API_CONTRACTS.md (if exists)
-    - .qa-output/codebase/TEST_SURFACE.md (if exists)
-    - .qa-output/codebase/TESTABILITY.md (if exists)
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: feature-test
-    codebase_map_dir: .qa-output/codebase
-    locator_registry: .qa-output/locators/LOCATOR_REGISTRY.md
-    </parameters>
-  "
-)
-
-6. If E2E test files were generated AND `--skip-run` was NOT passed, invoke the E2E runner to execute tests against the live app:
-
-Task(
-  prompt="
-    <objective>Run generated 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
-    - {generated E2E test files from executor return}
-    - {generated POM files from executor return}
-    </files_to_read>
-    <parameters>
-    app_url: {from --app-url flag or auto-detect}
-    output_dir: .qa-output
-    </parameters>
-  "
-)
-
-7. Present results:
-   - List generated files with type counts (unit, API, E2E, POM, fixture)
-   - If E2E runner executed: show pass/fail counts, locator fixes applied, app bugs found
-   - Suggest `/qa-pr` to package as a pull request
-
-$ARGUMENTS
+# Create Automated Tests
+
+Generate production-ready test files with POM pattern for a specific feature or module. Reads codebase map, existing analysis artifacts, and CLAUDE.md standards to produce tests that match the project's actual code patterns. If E2E tests are generated and an app URL is available, runs them against the live app and fixes locators until they pass.
+
+## Usage
+
+/create-test <feature-name> [--dev-repo <path>] [--app-url <url>] [--skip-run]
+
+- feature-name: which feature to test (e.g., "login", "checkout", "user API")
+- --dev-repo: path to developer repository (default: current directory)
+- --app-url: URL of running application for E2E test execution (auto-detects if not provided)
+- --skip-run: skip E2E execution, only generate and statically validate
+
+## What It Produces
+
+- Test spec files (unit, API, E2E as appropriate for the feature)
+- Page Object Model files (for E2E tests)
+- Fixture files (test data)
+- E2E_RUN_REPORT.md (if E2E tests were run against live app)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- POM rules, locator tiers, assertion rules, naming conventions, quality gates.
+2. Read existing analysis artifacts if available:
+   - `.qa-output/QA_ANALYSIS.md` -- architecture context
+   - `.qa-output/TEST_INVENTORY.md` -- pre-defined test cases for this feature
+3. Read codebase map if available (check `.qa-output/codebase/`):
+   - `CODE_PATTERNS.md` -- naming conventions, import style, code patterns to match
+   - `API_CONTRACTS.md` -- request/response shapes for API tests
+   - `TEST_SURFACE.md` -- function signatures and testable entry points
+   - `TESTABILITY.md` -- pure functions vs stateful code, mock boundaries
+   If codebase map does not exist, run `/qa-map` first for best results, or proceed without it.
+
+4. **Check existing locator registry and extract new locators from live app:**
+
+   a. **Check the locator registry first.** Read `.qa-output/locators/LOCATOR_REGISTRY.md` if it exists. This is the accumulated registry of all locators previously extracted from the live app. Check if locators for this feature's pages already exist.
+
+   b. **If locators for this feature's pages are already in the registry AND no `--app-url` was provided:** Skip browser extraction -- reuse existing locators. Print: `"Reusing cached locators for {feature} from registry."`
+
+   c. **If locators are missing or `--app-url` was provided:** Use the Playwright MCP to navigate the app and extract real locators BEFORE generating tests.
+
+   **Browser extraction process:**
+
+   1. Navigate to the feature's relevant pages:
+      ```
+      mcp__playwright__browser_navigate({ url: "{app_url}/{feature_path}" })
+      ```
+
+   2. Take an accessibility snapshot of each page to discover all interactive elements:
+      ```
+      mcp__playwright__browser_snapshot()
+      ```
+
+   3. Extract real locators from the snapshot -- collect:
+      - All `data-testid` attributes present on the page
+      - ARIA roles with accessible names (buttons, inputs, links, etc.)
+      - Form labels and placeholders
+      - Navigation structure and page layout
+
+   4. If the feature has multiple pages/views (e.g., login -> dashboard), navigate through the flow:
+      ```
+      mcp__playwright__browser_fill_form({ ... })
+      mcp__playwright__browser_click({ element: "..." })
+      mcp__playwright__browser_snapshot()  // capture next page
+      ```
+
+   5. Write per-feature locator file to `.qa-output/locators/{feature}.locators.md`:
+      ```markdown
+      # Locators -- {feature}
+
+      Extracted: {date}
+      App URL: {app_url}
+
+      ## Page: {page_name} ({url})
+
+      | Element | Locator Type | Locator Value | Tier |
+      |---------|-------------|---------------|------|
+      | Email input | data-testid | login-email-input | 1 |
+      | Password input | data-testid | login-password-input | 1 |
+      | Submit button | role + name | button "Log in" | 1 |
+      | Remember me | label | "Remember me" | 2 |
+
+      ## Page: {next_page} ({url})
+      ...
+      ```
+
+   6. Update the registry `.qa-output/locators/LOCATOR_REGISTRY.md` -- merge new locators into the central index:
+      ```markdown
+      # Locator Registry
+
+      Last updated: {date}
+      Total pages: {N}
+      Total locators: {N}
+
+      ## Index
+
+      | Feature | File | Pages | Locators | Extracted |
+      |---------|------|-------|----------|-----------|
+      | login | login.locators.md | 2 | 14 | 2026-03-25 |
+      | checkout | checkout.locators.md | 3 | 22 | 2026-03-25 |
+      | dashboard | dashboard.locators.md | 1 | 8 | 2026-03-25 |
+
+      ## All Locators by Page
+
+      ### /login
+      | Element | Locator Type | Locator Value | Tier | Source |
+      |---------|-------------|---------------|------|--------|
+      | Email input | data-testid | login-email-input | 1 | login.locators.md |
+      | ... | ... | ... | ... | ... |
+
+      ### /dashboard
+      ...
+      ```
+
+   If no app URL is available and no locators exist in the registry for this feature, skip this step -- the executor will propose locators based on source code analysis and CLAUDE.md conventions.
+
+5. Invoke executor agent to generate test files:
+
+Task(
+  prompt="
+    <objective>Generate test files for the specified feature following CLAUDE.md standards, using codebase map for context</objective>
+    <execution_context>@agents/qaa-executor.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    - .qa-output/locators/LOCATOR_REGISTRY.md (if exists -- accumulated real locators)
+    - .qa-output/locators/{feature}.locators.md (if exists -- feature-specific locators)
+    - .qa-output/codebase/CODE_PATTERNS.md (if exists)
+    - .qa-output/codebase/API_CONTRACTS.md (if exists)
+    - .qa-output/codebase/TEST_SURFACE.md (if exists)
+    - .qa-output/codebase/TESTABILITY.md (if exists)
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: feature-test
+    codebase_map_dir: .qa-output/codebase
+    locator_registry: .qa-output/locators/LOCATOR_REGISTRY.md
+    </parameters>
+  "
+)
+
+6. If E2E test files were generated AND `--skip-run` was NOT passed, invoke the E2E runner to execute tests against the live app:
+
+Task(
+  prompt="
+    <objective>Run generated 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
+    - {generated E2E test files from executor return}
+    - {generated POM files from executor return}
+    </files_to_read>
+    <parameters>
+    app_url: {from --app-url flag or auto-detect}
+    output_dir: .qa-output
+    </parameters>
+  "
+)
+
+7. Present results:
+   - List generated files with type counts (unit, API, E2E, POM, fixture)
+   - If E2E runner executed: show pass/fail counts, locator fixes applied, app bugs found
+   - Suggest `/qa-pr` to package as a pull request
+
+$ARGUMENTS

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

@@ -1,37 +1,37 @@
-# Full QA Audit
-
-Comprehensive quality audit of a test suite against CLAUDE.md standards. Scores across 6 dimensions: Locator Quality (20%), Assertion Specificity (20%), POM Compliance (15%), Test Coverage (20%), Naming Convention (15%), Test Data Management (10%).
-
-## Usage
-
-/qa-audit <path-to-tests> [--dev-repo <path>]
-
-- path-to-tests: directory containing test files to audit
-- --dev-repo: path to developer repository (for coverage cross-reference)
-
-## What It Produces
-
-- QA_AUDIT_REPORT.md -- 6-dimension scoring, critical issues list, prioritized recommendations with effort estimates
-
-## Instructions
-
-1. Read `CLAUDE.md` -- quality gates, locator tiers, assertion rules, POM rules, naming conventions.
-2. Invoke validator agent in audit mode:
-
-Task(
-  prompt="
-    <objective>Audit test suite quality and produce QA_AUDIT_REPORT.md with 6-dimension scoring</objective>
-    <execution_context>@agents/qaa-validator.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: audit
-    </parameters>
-  "
-)
-
-3. Present results with overall score and prioritized recommendations.
-
-$ARGUMENTS
+# Full QA Audit
+
+Comprehensive quality audit of a test suite against CLAUDE.md standards. Scores across 6 dimensions: Locator Quality (20%), Assertion Specificity (20%), POM Compliance (15%), Test Coverage (20%), Naming Convention (15%), Test Data Management (10%).
+
+## Usage
+
+/qa-audit <path-to-tests> [--dev-repo <path>]
+
+- path-to-tests: directory containing test files to audit
+- --dev-repo: path to developer repository (for coverage cross-reference)
+
+## What It Produces
+
+- QA_AUDIT_REPORT.md -- 6-dimension scoring, critical issues list, prioritized recommendations with effort estimates
+
+## Instructions
+
+1. Read `CLAUDE.md` -- quality gates, locator tiers, assertion rules, POM rules, naming conventions.
+2. Invoke validator agent in audit mode:
+
+Task(
+  prompt="
+    <objective>Audit test suite quality and produce QA_AUDIT_REPORT.md with 6-dimension scoring</objective>
+    <execution_context>@agents/qaa-validator.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: audit
+    </parameters>
+  "
+)
+
+3. Present results with overall score and prioritized recommendations.
+
+$ARGUMENTS

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

@@ -1,54 +1,54 @@
-# QA Repository Blueprint
-
-Generate a complete QA repository structure blueprint for a project that has no existing QA repo. Includes recommended stack, folder structure, config files, CI/CD pipeline, and definition of done.
-
-## Usage
-
-/qa-blueprint [--dev-repo <path>]
-
-- No arguments: analyzes current directory
-- --dev-repo: explicit path to developer repository
-
-## What It Produces
-
-- SCAN_MANIFEST.md -- dev repo scan with framework detection
-- QA_REPO_BLUEPRINT.md -- folder structure, recommended stack, config files, CI/CD strategy
-
-## Instructions
-
-1. Read `CLAUDE.md` -- repo structure, naming conventions, testing pyramid.
-2. Invoke scanner agent:
-
-Task(
-  prompt="
-    <objective>Scan developer repository and produce SCAN_MANIFEST.md</objective>
-    <execution_context>@agents/qaa-scanner.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-3. Invoke analyzer agent in full mode (blueprint):
-
-Task(
-  prompt="
-    <objective>Produce QA_REPO_BLUEPRINT.md with complete repository structure</objective>
-    <execution_context>@agents/qaa-analyzer.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/SCAN_MANIFEST.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: full
-    </parameters>
-  "
-)
-
-4. Present blueprint to user. No git operations.
-
-$ARGUMENTS
+# QA Repository Blueprint
+
+Generate a complete QA repository structure blueprint for a project that has no existing QA repo. Includes recommended stack, folder structure, config files, CI/CD pipeline, and definition of done.
+
+## Usage
+
+/qa-blueprint [--dev-repo <path>]
+
+- No arguments: analyzes current directory
+- --dev-repo: explicit path to developer repository
+
+## What It Produces
+
+- SCAN_MANIFEST.md -- dev repo scan with framework detection
+- QA_REPO_BLUEPRINT.md -- folder structure, recommended stack, config files, CI/CD strategy
+
+## Instructions
+
+1. Read `CLAUDE.md` -- repo structure, naming conventions, testing pyramid.
+2. Invoke scanner agent:
+
+Task(
+  prompt="
+    <objective>Scan developer repository and produce SCAN_MANIFEST.md</objective>
+    <execution_context>@agents/qaa-scanner.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    </parameters>
+  "
+)
+
+3. Invoke analyzer agent in full mode (blueprint):
+
+Task(
+  prompt="
+    <objective>Produce QA_REPO_BLUEPRINT.md with complete repository structure</objective>
+    <execution_context>@agents/qaa-analyzer.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    - .qa-output/SCAN_MANIFEST.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    mode: full
+    </parameters>
+  "
+)
+
+4. Present blueprint to user. No git operations.
+
+$ARGUMENTS

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

@@ -1,36 +1,36 @@
-# Fix Broken Tests
-
-Diagnose and fix broken test files. Classifies each failure as APPLICATION BUG, TEST CODE ERROR, ENVIRONMENT ISSUE, or INCONCLUSIVE. Auto-fixes only TEST CODE ERRORS. Never touches application code -- only reports APP BUGs for developer attention.
-
-## Usage
-
-/qa-fix <path-to-tests> [error output]
-
-- path-to-tests: directory or specific test files with failures
-- error output: paste test runner output (optional -- agent will run tests if not provided)
-
-## What It Produces
-
-- FAILURE_CLASSIFICATION_REPORT.md -- per-failure classification with evidence, confidence, and auto-fix log
-
-## Instructions
-
-1. Read `CLAUDE.md` -- classification rules, locator tiers, assertion quality.
-2. Invoke bug-detective agent:
-
-Task(
-  prompt="
-    <objective>Run tests, classify failures, and auto-fix TEST CODE ERRORS</objective>
-    <execution_context>@agents/qaa-bug-detective.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-3. Present results. APPLICATION BUGs are reported for developer action, not auto-fixed.
-
-$ARGUMENTS
+# Fix Broken Tests
+
+Diagnose and fix broken test files. Classifies each failure as APPLICATION BUG, TEST CODE ERROR, ENVIRONMENT ISSUE, or INCONCLUSIVE. Auto-fixes only TEST CODE ERRORS. Never touches application code -- only reports APP BUGs for developer attention.
+
+## Usage
+
+/qa-fix <path-to-tests> [error output]
+
+- path-to-tests: directory or specific test files with failures
+- error output: paste test runner output (optional -- agent will run tests if not provided)
+
+## What It Produces
+
+- FAILURE_CLASSIFICATION_REPORT.md -- per-failure classification with evidence, confidence, and auto-fix log
+
+## Instructions
+
+1. Read `CLAUDE.md` -- classification rules, locator tiers, assertion quality.
+2. Invoke bug-detective agent:
+
+Task(
+  prompt="
+    <objective>Run tests, classify failures, and auto-fix TEST CODE ERRORS</objective>
+    <execution_context>@agents/qaa-bug-detective.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    </parameters>
+  "
+)
+
+3. Present results. APPLICATION BUGs are reported for developer action, not auto-fixed.
+
+$ARGUMENTS

package/.claude/commands/qa-from-ticket.md

@@ -1,24 +1,24 @@
-# Create Tests from Ticket
-
-Generate test cases and executable test files from a ticket (Jira, Linear, GitHub Issue, or plain text user story). Combines the ticket's acceptance criteria with actual source code analysis to produce targeted, concrete tests. If an app URL is available, navigates the live app with Playwright MCP to extract real locators before generating tests.
-
-## Usage
-
-/qa-from-ticket <ticket-source> [--dev-repo <path>] [--app-url <url>]
-
-- ticket-source: one of:
-  - URL to GitHub/Jira/Linear issue
-  - Plain text user story or acceptance criteria
-  - File path to a .md or .txt with ticket details
-- --dev-repo: path to developer repository (default: current directory)
-- --app-url: URL of running application for browser-based locator extraction (auto-detects if not provided)
-
-## Instructions
-
-1. Read `CLAUDE.md` -- all QA standards.
-2. Execute the workflow:
-
-Follow the workflow defined in `@workflows/qa-from-ticket.md` end-to-end.
-Preserve all workflow gates (ticket parsing, traceability, validation).
-
-$ARGUMENTS
+# Create Tests from Ticket
+
+Generate test cases and executable test files from a ticket (Jira, Linear, GitHub Issue, or plain text user story). Combines the ticket's acceptance criteria with actual source code analysis to produce targeted, concrete tests. If an app URL is available, navigates the live app with Playwright MCP to extract real locators before generating tests.
+
+## Usage
+
+/qa-from-ticket <ticket-source> [--dev-repo <path>] [--app-url <url>]
+
+- ticket-source: one of:
+  - URL to GitHub/Jira/Linear issue
+  - Plain text user story or acceptance criteria
+  - File path to a .md or .txt with ticket details
+- --dev-repo: path to developer repository (default: current directory)
+- --app-url: URL of running application for browser-based locator extraction (auto-detects if not provided)
+
+## Instructions
+
+1. Read `CLAUDE.md` -- all QA standards.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-from-ticket.md` end-to-end.
+Preserve all workflow gates (ticket parsing, traceability, validation).
+
+$ARGUMENTS