Reviews a PR the way a strict test reviewer would when the code looks fine but the test coverage feels shaky. It calls out missing negative and boundary tests, gaps in integration coverage, flaky test risks, and spots where implementation changed but the matching tests didn't. Returns the critical missing tests first, then useful additional ones, described as sample test cases in plain English.
Reviews a pasted PR or diff in two passes instead of one: the first pass lists every potential issue it can find, and the second pass critiques those findings and throws out anything weak or unsupported. The final output separates confirmed issues from possible risks and lists discarded findings with the reason they didn't hold up, which cuts down on the false alarms a single-pass review tends to produce.
Generates unit tests for a single pasted function in whatever test framework you name, without needing a full diff or surrounding file for context.
Covers three buckets specifically: normal expected inputs, edge cases, and invalid inputs, written in your framework's syntax so the output can be dropped straight into a test file. A good default when you just have one function and need a quick, focused test pass.
Paste code along with its purpose, stack, module, and constraints to get a full-spectrum review covering correctness, security, performance, maintainability, error handling, accessibility, and test coverage in one pass. Returns a severity-ranked issues table, the top 3 priorities, positive observations, and specific tests to add — built to run right before merging a PR or handing code to a peer reviewer.
Generates a full test suite for a pasted code block, matched to your stated framework, test type, and existing test style so the output fits straight into the project.
Delivers a test plan table, happy-path and edge-case tests, error-case tests, mock setup for external dependencies, realistic test data, and a list of remaining coverage gaps — plus the runnable test code itself.
Paste a diff to get a fast, senior-engineer-style pass that prioritizes what actually matters — correctness bugs, regressions, security issues, missing tests, and maintainability risks — over style nitpicks. Each finding comes with severity, evidence pulled directly from the diff, and a concrete suggested change, making it a solid gate to run before opening a pull request.
Takes a single function plus its test framework (or "unknown" if you're not sure) and writes a practical test suite covering the main happy path, boundary cases, invalid inputs, and expected failure modes. It matches the project's existing test style when one is visible in the pasted context, and states any assumptions it made before showing the actual test code.