agentic-qe 3.12.3 → 3.13.1

package/.agents/skills/aqe-plan-quality/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: aqe-plan-quality
+description: Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or deciding which `.claude/agents/v3/qe-*.md` capabilities should inform a task. Do not use merely to execute an already-defined test command.
+---
+
+# Plan AQE Quality
+
+1. Read `AGENTS.md`, the requested change, and the affected public boundaries.
+2. Inspect the closest implementation and tests before proposing work.
+3. Classify the risk domains using [references/qe-routing.md](references/qe-routing.md).
+4. Select only the QE specialties needed. Treat Claude agent definitions as
+   domain references; do not copy their Claude-only `Task`, `SendMessage`, or
+   hook syntax into Codex actions.
+5. Produce a plan that covers:
+   - observable requirements and acceptance criteria;
+   - affected boundaries, dependencies, and failure modes;
+   - durable tests first, then implementation-coupled tests;
+   - security, performance, accessibility, contract, or resilience checks when
+     triggered by the change;
+   - the narrowest repository verification commands.
+6. Flag assumptions, unavailable environments, destructive operations, and
+   decisions requiring human approval.
+
+Prefer evidence from repository code and configuration over generic test
+checklists. Keep the selected fleet small and explain each specialty’s purpose.

package/.agents/skills/aqe-plan-quality/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "AQE Plan Quality"
+  short_description: "Build risk-based QE plans with the AQE fleet"
+  default_prompt: "Use $aqe-plan-quality to create a risk-based quality plan for this change."

package/.agents/skills/aqe-plan-quality/references/qe-routing.md

@@ -0,0 +1,22 @@
+# QE Routing Reference
+
+Use the shipped definitions in `.claude/agents/v3/qe-*.md` as detailed domain
+references. The principal routing map is:
+
+| Need | QE specialties |
+| --- | --- |
+| Requirements and testability | `qe-requirements-validator`, `qe-bdd-generator`, `qe-product-factors-assessor`, `qe-quality-criteria-recommender` |
+| Test design and implementation | `qe-test-architect`, `qe-tdd-specialist`, `qe-property-tester`, `qe-integration-tester`, `qe-test-idea-rewriter` |
+| Execution and reliability | `qe-parallel-executor`, `qe-flaky-hunter`, `qe-retry-handler` |
+| Coverage and effectiveness | `qe-coverage-specialist`, `qe-gap-detector`, `qe-mutation-tester` |
+| Code impact | `qe-code-intelligence`, `qe-dependency-mapper`, `qe-impact-analyzer`, `qe-kg-builder`, `qe-code-complexity` |
+| Defect analysis | `qe-regression-analyzer`, `qe-root-cause-analyzer`, `qe-defect-predictor` |
+| Quality decision | `qe-risk-assessor`, `qe-quality-gate`, `qe-deployment-advisor`, `qe-devils-advocate` |
+| Security | `qe-security-scanner`, `qe-security-auditor`, `qe-pentest-validator`, `qe-sod-analyzer` |
+| Contract and integration | `qe-contract-validator`, `qe-graphql-tester`, `qe-soap-tester`, `qe-odata-contract-tester`, `qe-message-broker-tester`, `qe-middleware-validator`, `qe-sap-rfc-tester`, `qe-sap-idoc-tester` |
+| Performance and resilience | `qe-performance-tester`, `qe-load-tester`, `qe-chaos-engineer` |
+| UX and accessibility | `qe-visual-tester`, `qe-responsive-tester`, `qe-accessibility-auditor`, `qe-qx-partner` |
+| Learning | `qe-pattern-learner`, `qe-learning-coordinator`, `qe-metrics-optimizer`, `qe-transfer-specialist` |
+| Cross-domain coordination | `qe-fleet-commander`, `qe-queen-coordinator` |
+
+Select the smallest set that covers the actual change.

package/.agents/skills/aqe-review-quality/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: aqe-review-quality
+description: Review Agentic QE changes and issue an evidence-backed quality verdict. Use for code review, regression-risk assessment, release readiness, quality-gate evaluation, security/performance/testability review, or checking whether a change has sufficient verification. Do not use when the user primarily asks to implement a feature.
+---
+
+# Review AQE Quality
+
+1. Read `AGENTS.md`, the diff or requested scope, affected implementation,
+   tests, and configuration.
+2. Review for correctness first: broken behavior, data loss, security,
+   concurrency, compatibility, and missing error paths.
+3. Use [references/quality-gates.md](references/quality-gates.md) to select
+   relevant QE review lenses. Do not run unrelated broad scans.
+4. Verify claims with focused commands where safe and available. Distinguish
+   observed failures from inferred risks.
+5. Report findings by severity with file and line references, the triggering
+   scenario, and the smallest useful remediation.
+6. End with one verdict:
+   - `PASS`: no material finding and adequate evidence;
+   - `CONDITIONAL`: bounded risks or missing environment-dependent evidence;
+   - `FAIL`: correctness, safety, compatibility, or verification blocker.
+7. List the exact checks run and any checks not run.
+
+Do not edit code during a review unless the user also asks for fixes.

package/.agents/skills/aqe-review-quality/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "AQE Review Quality"
+  short_description: "Assess change risk and enforce AQE quality gates"
+  default_prompt: "Use $aqe-review-quality to review this change and produce a quality verdict."

package/.agents/skills/aqe-review-quality/references/quality-gates.md

@@ -0,0 +1,20 @@
+# AQE Quality Gates
+
+Apply only relevant gates:
+
+| Gate | Blocking signal |
+| --- | --- |
+| Correctness | A realistic input violates the stated behavior or invariant |
+| Data safety | A path can corrupt, overwrite, or silently lose persisted data |
+| Security | Authorization bypass, injection, secret exposure, unsafe path, or unvalidated boundary |
+| Compatibility | Public API, CLI, MCP, schema, or shipped asset changes without migration/compatibility handling |
+| Test adequacy | Changed behavior lacks a durable assertion or the test cannot detect a plausible defect |
+| CLI/MCP parity | Equivalent surfaces behave differently or only one was verified |
+| Reliability | Race, leak, retry masking, nondeterministic result, or unbounded resource use |
+| Performance | Measured regression beyond an established threshold |
+| Distribution | `.claude/agents/v3`, `assets/agents/v3`, manifests, or generated bundles are out of sync |
+| Release evidence | Required build, invariant, parity, or smoke check failed or was not run |
+
+Use `.claude/agents/v3/qe-quality-gate.md`,
+`qe-risk-assessor.md`, `qe-deployment-advisor.md`, and the domain-specific QE
+definitions as deeper references when a gate needs specialized criteria.

package/.agents/skills/aqe-test-change/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: aqe-test-change
+description: Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.
+---
+
+# Test an AQE Change
+
+1. Read `AGENTS.md`, the changed code, nearby tests, and relevant public
+   interfaces.
+2. Reproduce a reported defect with the exact scenario before changing code.
+3. Identify the affected QE specialty from
+   [references/test-specialties.md](references/test-specialties.md).
+4. Add tests in this order:
+   - durable boundary contracts, invariants, or properties;
+   - integration behavior across affected components;
+   - focused unit examples needed for the red-green loop.
+5. Keep tests deterministic. Do not hide failures with retries, skips, weakened
+   assertions, fabricated fixtures, or mocks of the behavior under test.
+6. Run the narrowest matching Vitest target first. Expand to typecheck, build,
+   agent/skill parity, MCP integration, or full CI checks in proportion to the
+   changed surface.
+7. For capabilities exposed through both CLI and MCP, verify both paths.
+8. Report commands, pass/fail counts, limitations, and untested external
+   dependencies.
+
+Never modify or reset `.agentic-qe/memory.db`. Use a copy for any database test.

package/.agents/skills/aqe-test-change/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "AQE Test Change"
+  short_description: "Design and verify durable tests for code changes"
+  default_prompt: "Use $aqe-test-change to test and verify this code change."

package/.agents/skills/aqe-test-change/references/test-specialties.md

@@ -0,0 +1,23 @@
+# Test Specialty Selection
+
+- Public algorithm or data structure: invariants and property tests; consult
+  `qe-property-tester` and `qe-test-architect`.
+- CLI behavior: command-level test plus the equivalent MCP check when exposed;
+  consult `qe-integration-tester`.
+- MCP handler or protocol: handler tests are insufficient by themselves; add a
+  protocol-level integration check.
+- Coverage gap: inspect risk and branch behavior before adding examples; consult
+  `qe-coverage-specialist`, `qe-gap-detector`, and `qe-mutation-tester`.
+- Intermittent failure: preserve evidence and classify nondeterminism; consult
+  `qe-flaky-hunter` and `qe-root-cause-analyzer`.
+- API/schema change: test backward compatibility and negative cases; consult
+  `qe-contract-validator` or the protocol-specific QE definition.
+- Security boundary: test authorization, input validation, path safety, secret
+  handling, and failure disclosure; consult `qe-security-auditor`.
+- Performance-sensitive path: measure a baseline and regression threshold;
+  consult `qe-performance-tester`.
+- Browser or UI change: cover keyboard/accessibility, responsive layout, and
+  stable visual evidence where relevant.
+
+Repository test commands are defined in `package.json`; follow `AGENTS.md` for
+the recommended narrow-to-broad sequence.

package/.claude/helpers/.helpers-version

@@ -1 +1 @@
-3.25.4
+3.32.2