Use when reviewing a pull request, branch, or set of code changes for correctness, security, performance, and style issues. Resolves a PR URL, PR number, branch name, or natural-language description into the actual diff, then produces an actionable in-chat review with severity-tagged comments grouped by category, plus concrete unified-diff patches for blockers.
OutcomeWalk a PR or branch and deliver an actionable, in-chat code review grouped by category (correctness, security, performance, style) with severity tags and concrete patches for blockers.
Use when you want to drive a feature implementation through a strict test-driven cycle of failing-test, minimal-pass, and refactor commits on the current branch.
OutcomeThe feature described in the spec is implemented and covered by a passing test that was written before the implementation, with the work delivered in clean red-green-refactor order on the current branch.
Use when drafting a markdown changelog entry from a git commit range, with user-facing language up top and a smaller technical details section beneath.
OutcomeProduce a markdown changelog entry for a git commit range, written for users at the top with a smaller technical details section beneath.
