| name | sdk-verification-matrix |
| description | Determine and enforce the correct zksync-js verification loops (fast, adapter e2e, docs) based on changed files, PR completion state, and CI failure context. |
| metadata | {"short-description":"Route changes to required verification loops"} |
SDK Verification Matrix
Use this skill to standardize change verification and avoid incomplete test coverage.
Use This Skill When
- Preparing a PR for review/merge
- Triage is needed for CI failures
- A task asks for test verification or debugging
Use explicit invocation as $sdk-verification-matrix at PR finalization and on CI failures.
Verification Policy
Fast Loop (always required)
Run:
bun run lint
bun run format:check
bun run typecheck
bun run test
Adapter Loop (conditional)
Run:
bun run test:e2e:ethers
bun run test:e2e:viem
Trigger rules:
- If
src/core/** changed: run both adapter e2e suites.
- If only
src/adapters/ethers/** changed: run ethers e2e; run viem e2e if parity impact is plausible.
- If only
src/adapters/viem/** changed: run viem e2e; run ethers e2e if parity impact is plausible.
Docs Loop (conditional)
Run:
bun run docs:build
Trigger when changes touch:
Responsibilities
- Determine required loops from touched files and task context.
- State command set with rationale before execution.
- Report pass/fail/blocker outcomes by loop.
- Escalate missing-loop risk when required suites were skipped.
Output Format
Provide:
- Required loops and why
- Commands run (or required to run)
- Loop status (
pass, fail, blocked)
- Failures with reproduction command
References
