midnight-cq

Use this agent to audit a Midnight project's code quality setup and produce a detailed report with recommendations. Checks Biome configuration, Vitest setup, Playwright config, Husky hooks, CI workflows, test quality, and coverage gaps. Read-only — never modifies files. Example 1: "Review my project's code quality setup" — scans for all CQ tooling and validates against Midnight standards. Example 2: "Are my tests good enough?" — analyzes test files for coverage gaps, missing error assertions, unused simulator features. Example 3: "Is my CI configured correctly?" — validates workflow files against the recommended two-workflow pattern.

Use this agent to run all code quality checks on a Midnight project and produce a structured report interpreting the results. Executes Biome linting, TypeScript type checking, Compact compilation, Vitest tests, and Playwright E2E tests. Read-only — runs checks but never modifies files. Example 1: "Run all quality checks" — executes the full suite and reports results with explanations and fix recommendations. Example 2: "Why are my tests failing?" — runs vitest, captures output, interprets simulator errors, and suggests fixes. Example 3: "Check if my code is ready to push" — runs the same checks as the pre-push hook and reports any issues.

This skill should be used when the user asks to write Compact contract tests, test a contract with the simulator, set up createSimulator, mock contract patterns, override witnesses in tests, write unit tests for Compact circuits, set up Vitest for a Compact project, test access control or error cases, use describe.each or it.each for parameterized tests, check invariants with afterEach, property-based testing with fast-check, or ZK commitment testing.

This skill should be used when the user asks to test DApp Connector API integration, test wallet connection, test makeTransfer, test balanceTransaction, test submitTransaction, mock ConnectedAPI, stub wallet for tests, test wallet errors, test PermissionRejected, test Disconnected handling, test progressive enhancement, write wallet integration tests, test DApp Connector error codes, test wallet discovery, test window.midnight, test apiVersion, test signData, or test DApp Connector security.

This skill should be used when the user asks to test my dapp, write e2e tests, test wallet connection, playwright midnight, test transaction UI, integration test frontend, end-to-end test, browser test, test UI with contract, write Playwright tests for a Midnight dapp, mock ContractProvider, test wallet disconnect, test confirmation screen, test rejected transaction, test contract state displayed in the UI, test React components with contract simulator, mock wallet in tests, or set up e2e testing. NOT for testing Compact contract logic in isolation — see midnight-cq:compact-testing.

This skill should be used when the user asks to write ledger tests, test transaction construction, test proof staging, test ZswapLocalState, test DustLocalState, test cost model, test coinCommitment, test ledger-v8, test onchain-runtime, or test well-formedness. Also triggered by requests to write tests for code that uses @midnight-ntwrk/ledger-v8 or @midnight-ntwrk/onchain-runtime directly, test proof staging lifecycle, test token type functions, test crypto fixtures, test serialization round-trips for ledger types, test fee estimation, test SyntheticCost, or test coinNullifier.

This skill should be used when the user asks to run linting, check code quality, run tests, or needs help with "why is biome failing", "fix lint errors", "CI is failing", "type check errors", "biome error", "vitest failing", "tsc error", "playwright failing", or "e2e tests failing". Also triggered by requests to interpret Biome output, fix tsc errors in Midnight projects, debug vitest failures with simulator stack traces, run the full pre-push suite, or understand why compact compile is failing.