Fill in the feature you want built, the language, and up to three specific requirements, and get an implementation request structured enough that nothing important gets skipped. It explicitly asks for error handling, edge cases, performance, and framework best practices to be considered up front, and instructs the output to keep existing comments intact and explain its own logic inline.
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.
Summarizes a pasted diff in exactly three bullets for a reviewer who has never seen this codebase: what changed, why it changed, and what could go wrong.
It's built to name real classes, functions, and file paths rather than describe changes abstractly, and it doubles as a scope check — if the diff can't be summarized in three concrete bullets, the PR is probably too big.
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.