gavel

Creates and executes API tests using the service layer pattern. Handles authentication, tenant/context headers, factories, contract validation, and error matchers. Covers happy path, validation, auth, authorization, and edge cases through the repo's native API test stack.

Audits expected-failure, skip, ignore, disabled, quarantine, and WIP markers across test suites. Runs each marked test, categorizes as real bug, isolation issue, undocumented marker, or already-fixed marker. Produces a report and edits only when a marker is safe to remove.

Creates automated E2E tests using stack-native patterns. Uses fixture DI, factories, native assertions, and the repo's existing composition model. Writes test by test with intermediate validation. Adapts by detected capabilities rather than hardcoded framework recipes.

Debugs and fixes failing tests via systematic root cause analysis. Determines if failure is test issue, app bug, or env issue. Validates with test run + verification after each fix. Framework-adaptive — uses the correct debugging approach per active profile.

Analyzes new backend/frontend commits after git pull to determine if API or UI automation needs updates, new tests, or refactors. Use when commits have landed and QA needs to decide whether to write/update tests. Framework-adaptive — works with any automation repo structure.

Analyze test suite run results for any framework. Classify failures as env, seed, app bug, test bug, or expected fail. Produce pass-rate by area and ranked recommendations. Use after any test suite run.

Author API tests using the service-layer pattern in the target repo. Generates test code only — not OpenAPI governance, contract platforms, or env provisioning. Framework-adaptive. Use when asked to write API tests with existing patterns.

Whole-repo audit for test suite bloat and Test Constitution violations. Scans the entire codebase: unused POMs, dead locators, duplicate factories, orphaned tests, CSS/XPath overuse, hardcoded data, missing test.step(). Ranked list of what to delete, simplify, or fix. Use when the user says "audit this test suite", "gavel-audit", "/gavel-audit", "find test bloat", or "what's wrong with my tests". One-shot report, does not apply fixes.

Multi-tenant firm-scoped authentication for API and UI tests. Use when tests get 401 across tenants, need tenant-scoped tokens, or debug firm-scope mismatches. Framework-adaptive.

Writes standardized bug reports when an automated test confirms a real product defect. Use only after gavel-heal or gavel-analyze classifies APP BUG — not for flaky, env, or test-side failures.

3 hooks across 3 events