▸case-01 I've refactored the shared utility functions across two packages in our monorepo. Please execute the necessary checks to confirm nothing broke, and give me a summary report showing all commands run, their pass/fail results, and anything that couldn't be run. | fail→fail | 5,042 | 15,565 | +209% | 1 | 1 | 0% | 289 | 615 | +113% | 0 | 0 | — |
▸case-02 I updated our Docker setup and deployment files for local development. Can you run a complete validation of these configuration changes and output a report detailing the steps taken, test outputs, and any remaining blockers? | fail→fail | 8,085 | 4,413 | -45% | 1 | 1 | 0% | 1,296 | 443 | -66% | 0 | 0 | — |
▸case-03 We just revised the navigation bar component and its associated styling. Please perform runtime verification for these visual and behavior changes, then provide a full report containing the test steps, actual proof of functionality, and a list of any skipped checks. | fail→fail | 4,308 | 4,222 | -2% | 1 | 1 | 0% | 171 | 427 | +150% | 0 | 0 | — |
▸case-04 We have a TypeScript monorepo where I just modified the payload parser in `@app/parser`. I want you to run the test and build scripts right away using standard pnpm commands like `pnpm --filter @app/parser test` and `pnpm --filter @app/parser build`. Skip inspecting configuration files to save time. | fail→fail | 6,878 | 8,771 | +28% | 1 | 1 | 0% | 711 | 760 | +7% | 0 | 0 | — |
▸case-17 When starting verification for a modified backend package in our workspace, what is the initial sequence of inspection steps before choosing checks? | fail→pass | 13,779 | 2,821 | -80% | 1 | 1 | 0% | 2,088 | 650 | -69% | 0 | 0 | — |
▸case-05 I made changes to the billing webhooks handler in our Node service repository. Before deciding on the verification commands to execute, should you check references/verification-matrix.md or should you rely solely on standard npm package scripts? | pass→pass | 5,485 | 2,927 | -47% | 1 | 1 | 0% | 855 | 763 | -11% | 0 | 0 | — |
▸case-06 I updated a single utility function inside package `packages/utils/src/formatDate.ts` that is only used locally within that package. Should we immediately execute full monorepo end-to-end regression suites and all package builds across 15 microservices, or choose a narrower check? | pass→pass | 11,181 | 4,873 | -56% | 1 | 1 | 0% | 1,889 | 1,066 | -44% | 0 | 0 | — |
▸case-07 I fixed a regex validation error in `packages/validator/src/email.ts`. The validator package has a dedicated test script `test:unit` defined in its package.json. How should tests be executed for this change? | pass→fail | 9,155 | 6,763 | -26% | 1 | 1 | 0% | 1,404 | 1,488 | +6% | 0 | 0 | — |
▸case-08 After fixing a bug in the shared UI component library `packages/ui`, I ran `npm test`. The tests passed. Is verification complete for `packages/ui`, or does the package build step also need to be run? | pass→pass | 10,274 | 5,616 | -45% | 1 | 1 | 0% | 1,662 | 1,247 | -25% | 0 | 0 | — |
▸case-09 I updated a shared TypeScript interface in `packages/common` that is imported by four different backend services and two frontend apps. Is running `npm run build` inside `packages/common` sufficient to verify this change across the project? | pass→pass | 10,898 | 5,693 | -48% | 1 | 1 | 0% | 1,805 | 1,167 | -35% | 0 | 0 | — |
▸case-10 I modified `docker-compose.yml` to update environment variables and network settings for our services. To verify this deployment change, is it enough to run `docker compose up -d` with the default configuration file? | fail→pass | 9,708 | 5,083 | -48% | 1 | 1 | 0% | 1,691 | 1,080 | -36% | 0 | 0 | — |
▸case-11 We updated the CSS and layout of the checkout button component in `apps/storefront`. I ran `tsc --noEmit` and it passed with zero errors. Can we mark visual and runtime verification as complete based on this passing typecheck? | pass→pass | 8,943 | 4,964 | -44% | 1 | 1 | 0% | 1,514 | 1,063 | -30% | 0 | 0 | — |
▸case-12 During verification of our API gateway changes, the unit tests passed and package build succeeded, but the local Redis container failed to start, blocking integration test execution. How should this result be structured in the final report? | pass→pass | 10,051 | 6,691 | -33% | 1 | 1 | 0% | 1,681 | 1,324 | -21% | 0 | 0 | — |
▸case-13 Our team fixed a runtime null pointer exception in `apps/web/src/checkout.ts`. A developer claims that because `npx tsc` outputs zero errors, the bug is proven fixed at runtime. How should we evaluate this claim? | pass→pass | 13,494 | 10,997 | -19% | 1 | 1 | 0% | 2,039 | 1,508 | -26% | 0 | 0 | — |
▸case-14 We implemented a complex multi-step document approval workflow in `apps/admin`. During verification, the backend service started successfully and `POST /api/v1/auth/login` returned a 200 OK status code. Does this successful authentication log in prove that the document approval workflow functions correctly? | pass→pass | 9,710 | 5,646 | -42% | 1 | 1 | 0% | 1,598 | 1,187 | -26% | 0 | 0 | — |
▸case-15 During project verification for a user registration bug fix, the user registration unit test failed due to an unhandled promise rejection. However, 45 other package builds and unit tests in unrelated packages passed. Is it acceptable to mark the overall verification status as PASS since 98% of checks succeeded? | pass→pass | 8,668 | 4,509 | -48% | 1 | 1 | 0% | 1,390 | 981 | -29% | 0 | 0 | — |
▸case-16 I ran three manual curl requests against our auth endpoints and checked that they returned expected HTTP 200 responses. Can I state in the verification report that our test coverage for the auth package is now at 85%? | pass→pass | 10,181 | 4,089 | -60% | 1 | 1 | 0% | 1,532 | 905 | -41% | 0 | 0 | — |
▸case-18 We updated `docker-compose.override.yml` and `docker-compose.standalone-infra.yml` to add local caching. What specific compose configurations must be tested during verification? | pass→pass | 14,860 | 3,002 | -80% | 1 | 1 | 0% | 2,491 | 702 | -72% | 0 | 0 | — |
▸case-19 A designer asked us to update the header color scheme and font weights in `apps/docs`. We ran the build script and it completed without errors. Is this build success sufficient evidence for visual design verification? | pass→pass | 9,851 | 4,895 | -50% | 1 | 1 | 0% | 1,468 | 933 | -36% | 0 | 0 | — |
▸case-20 We changed the database schema model in `packages/db` which is referenced by `apps/api` and `apps/worker`. What build scope should be executed to verify this change? | pass→fail | 9,439 | 5,123 | -46% | 1 | 1 | 0% | 1,534 | 455 | -70% | 0 | 0 | — |
▸case-21 After running unit tests and builds for an API refactor, two integration tests were skipped due to missing API keys. Should these skipped tests be left out of the final summary report to avoid confusion? | pass→pass | 9,150 | 7,965 | -13% | 1 | 1 | 0% | 1,440 | 1,460 | +1% | 0 | 0 | — |
▸case-22 I have a TypeScript function `calculateTax(amount: number, rate: number): number` in `packages/billing/src/tax.ts`. Please write a complete Vitest unit test file with mock data and assertions for edge cases like zero amount and negative rate. | pass→fail | 13,489 | 12,581 | -7% | 1 | 1 | 0% | 2,696 | 451 | -83% | 0 | 0 | — |
▸case-23 Please write a GitHub Actions workflow YAML file (`.github/workflows/ci.yml`) for a Node.js monorepo that runs npm install, caches node_modules, and executes npm test on every pull request to main. | pass→fail | 11,146 | 4,385 | -61% | 1 | 1 | 0% | 2,018 | 444 | -78% | 0 | 0 | — |
▸case-24 We need a k6 load testing script in JavaScript to benchmark our `/api/v1/products` endpoint with 50 virtual users over 2 minutes, asserting that the 95th percentile response time is under 200ms. | pass→fail | 6,603 | 3,977 | -40% | 1 | 1 | 0% | 1,277 | 441 | -65% | 0 | 0 | — |