▸case-01 Please review this pull request diff for any verification gaps or untested assumptions in the new payment processing handler. Check if all state transitions have adequate verification or if there are missing test cases. | fail→fail | 13,020 | 6,587 | -49% | 1 | 1 | 0% | 541 | 920 | +70% | 0 | 0 | — |
▸case-02 I'd like an audit of our authentication architecture proposal to identify any verification gaps. Can you check whether all security claims and edge cases in the spec actually have corresponding validation strategies? | fail→fail | 8,657 | 9,758 | +13% | 1 | 1 | 0% | 1,259 | 1,485 | +18% | 0 | 0 | — |
▸case-03 Can you examine the refactored database migration scripts and test files to spot any verification gaps? We want to make sure every data transformation step is properly validated before releasing. | fail→fail | 9,793 | 6,881 | -30% | 1 | 1 | 0% | 1,232 | 1,037 | -16% | 0 | 0 | — |
▸case-04 Write unit tests using Jest for an Express.js Stripe payment webhook endpoint in webhook.test.js to achieve complete coverage for signature verification and charge failure paths. | pass→fail | 18,866 | 7,294 | -61% | 1 | 1 | 0% | 3,616 | 1,122 | -69% | 0 | 0 | — |
▸case-05 Refactor the PostgreSQL database migration script in Knex.js (20231012_add_indexes.js) to apply non-blocking index creation using concurrent index creation. | pass→fail | 17,874 | 15,678 | -12% | 1 | 1 | 0% | 3,032 | 3,153 | +4% | 0 | 0 | — |
▸case-06 Implement a JWT token refresh middleware function in Go for an OAuth2 server using the golang-jwt/jwt library in middleware.go. | pass→fail | 22,902 | 6,240 | -73% | 1 | 1 | 0% | 4,676 | 842 | -82% | 0 | 0 | — |
▸case-07 Audit the gRPC inventory service specification in inventory.proto and its test file inventory_test.go for verification gaps. The spec includes comprehensive unit, integration, and failure mode tests for all RPC methods. Output the review in markdown format, providing a single-line summary if no gaps exist. | fail→pass | 15,722 | 11,402 | -27% | 1 | 1 | 0% | 2,582 | 1,090 | -58% | 0 | 0 | — |
▸case-08 Review the Redis distributed lock implementation in lock.py for verification gaps. The lock implementation contains non-standard clock skew risks that fall outside standard gap shapes (gap_shape: other). Render the analysis in pure markdown without JSON, placing custom gap shapes under an Other findings heading. | pass→pass | 21,365 | 17,716 | -17% | 1 | 1 | 0% | 2,897 | 2,606 | -10% | 0 | 0 | — |
▸case-09 Review the Kubernetes custom resource controller code in cluster_controller.go for DatabaseCluster CRDs. While code style and memory allocation issues may exist, restrict your findings exclusively to verification gaps such as unverified reconcile loops. Format output in pure markdown. | pass→pass | 20,184 | 14,069 | -30% | 1 | 1 | 0% | 2,157 | 1,153 | -47% | 0 | 0 | — |
▸case-10 Audit the Apache Kafka consumer group handler in consumer.go for verification gaps during consumer rebalance events. Present the analysis strictly in markdown text format without wrapping results in JSON code blocks. | pass→pass | 36,383 | 23,161 | -36% | 1 | 1 | 0% | 3,770 | 3,806 | +1% | 0 | 0 | — |
▸case-11 Review the GraphQL user mutation schema in schema.graphql and its test suite mutation_test.ts. Every mutation field (createUser, updateUser, deleteUser) has complete positive and negative test coverage. Output the review as plain text, returning the single-line clean status if no gaps exist. | pass→pass | 11,042 | 5,817 | -47% | 1 | 1 | 0% | 1,899 | 940 | -51% | 0 | 0 | — |
▸case-12 Examine the AWS Lambda event handler in lambda_function.py processing DynamoDB Streams. Note that batch failure retries and dead-letter queue routing lack unit test assertions. Provide the evaluation in markdown format without JSON structures. | pass→pass | 30,175 | 11,833 | -61% | 1 | 1 | 0% | 3,275 | 1,924 | -41% | 0 | 0 | — |
▸case-13 Review the Stripe payment webhook handler in webhooks.rs for verification gaps. The handler lacks verification for concurrent duplicate webhook deliveries (gap_shape: other). Render in pure markdown without JSON, grouping uncategorized shapes under an Other findings header. | fail→pass | 17,774 | 7,721 | -57% | 1 | 1 | 0% | 2,958 | 1,288 | -56% | 0 | 0 | — |
▸case-14 Audit the Terraform module for AWS S3 bucket policies in main.tf and terratest/s3_test.go. Ensure all policy enforcement rules have automated Terratest coverage. Output findings strictly in markdown without JSON. | pass→fail | 26,398 | 9,986 | -62% | 1 | 1 | 0% | 4,952 | 1,515 | -69% | 0 | 0 | — |
▸case-15 Review the React custom hook useAsyncData.ts and its test file useAsyncData.test.ts. Pending, success, error, retry, and cleanup state transitions are fully covered by tests. If zero verification gaps exist, output only the single-line summary status. | fail→pass | 5,686 | 5,792 | +2% | 1 | 1 | 0% | 772 | 1,040 | +35% | 0 | 0 | — |
▸case-16 Analyze the OAuth 2.0 PKCE authorization code handler in oauth_controller.py. The handler validates code_verifier parameters, but lacks tests for invalid PKCE code_challenge mismatches. Output the review in markdown format without JSON. | pass→pass | 19,165 | 11,700 | -39% | 1 | 1 | 0% | 3,436 | 1,738 | -49% | 0 | 0 | — |
▸case-17 Audit the multi-stage Dockerfile and container test spec container_test.yaml for a Node.js web application. Automated tests cover image size limits, non-root execution, and secret file exclusion. Output the single-line clean status message if no gaps are found. | fail→pass | 11,206 | 42,950 | +283% | 1 | 1 | 0% | 1,375 | 1,256 | -9% | 0 | 0 | — |
▸case-18 Examine the Resilience4j circuit breaker configuration in OrderService.java and OrderServiceTest.java. Fallback method execution during open-state transitions is untested. Present the evaluation in pure markdown format without JSON. | pass→pass | 16,701 | 16,122 | -3% | 1 | 1 | 0% | 2,713 | 2,685 | -1% | 0 | 0 | — |
▸case-19 Audit the WebSocket connection manager in ws_manager.js for verification gaps. The sliding window timer for heartbeat timeouts represents a non-standard gap (gap_shape: other). Format as pure markdown without JSON, placing non-standard gaps under an Other findings heading. | pass→pass | 13,225 | 8,547 | -35% | 1 | 1 | 0% | 1,933 | 1,188 | -39% | 0 | 0 | — |
▸case-20 Review the FastAPI JWT token revocation middleware in auth.py and test_auth.py. Token revocation checks during Redis cluster failovers lack test verification. Present findings in markdown without JSON code blocks. | pass→pass | 26,448 | 17,244 | -35% | 1 | 1 | 0% | 4,431 | 2,817 | -36% | 0 | 0 | — |
▸case-21 Audit the Rust Tokio bounded async channel worker in worker.rs and its test suite tests/worker_test.rs. Unit and property-based tests cover channel closure, backpressure, and task panic handling. Return the single-line clean status line if no verification gaps exist. | fail→pass | 6,362 | 14,654 | +130% | 1 | 1 | 0% | 882 | 2,218 | +151% | 0 | 0 | — |
▸case-22 Review the Elasticsearch Index Lifecycle Management policy in ilm_policy.json and test script ilm_test.py. High disk usage rollover triggers are unverified in test cases. Output the review in pure markdown format. | pass→pass | 20,207 | 10,100 | -50% | 1 | 1 | 0% | 3,374 | 1,566 | -54% | 0 | 0 | — |
▸case-23 Examine the gRPC tracing interceptor in tracing_interceptor.go and interceptor_test.go. Distributed context propagation across async goroutines is untested. Output findings in markdown format without JSON. | pass→pass | 22,451 | 28,536 | +27% | 1 | 1 | 0% | 2,749 | 4,931 | +79% | 0 | 0 | — |