Turn a code fix into a review checklist
Using Codex CLI where available: Supply a public patch and authorized code to list related files, concerns and suggested tests.
Using Codex CLI where available: Supply a public patch and authorized code to list related files, concerns and suggested tests.
Using Claude where available: Supply an original article, audience and length limits to get draft posts with sources and open checks.
Using Codex CLI where available: Supply authorized code and approved rules to generate test inputs and record reproducible failures.
Using Codex CLI where available: Supply an existing game copy and level requirements to make a bounded change with test evidence and unfinished work.
Using Claude where available: Supply one page and confirmed new information to get proposed edits, conflicts and a revised draft.
Using Claude where available: Supply sanitized receipts, manuals and past records to build an equipment history with source references.
Using Claude where available: Supply a transcript and available apps and displays to get a layout preview and clarification questions.
Using ChatGPT where available: Supply an authorized practice board and rules to transcribe tile feedback, then test candidate words against it.
Using Claude where available: Supply dates, time zones, duration and working hours to get candidate slots and draft poll wording.
Using Claude where available: Supply dimensions, allowed parts and intended use to get a model plan, part IDs and connection risks.
Using Claude where available: Supply an original layout and device requirements to get a room-connection map, camera controls and route checks.
Using Claude where available: Supply a game’s starting state, rules and goals to design a comparison or analyze existing logs.
Using Claude where available: Supply quotes for the same route, dates and cabin to separate cash, points, fees and change conditions.
Using Claude where available: Supply simulated memory, network and message limits to draft disconnection, restart and data-retention checks.
Using Claude where available: Supply approved experience facts and a job description to get a resume draft, change list and evidence gaps.
Using Claude where available: Supply a small problem, known baseline and research limits to separate conjectures, candidate solutions and checking methods.
Using Claude where available: Supply example rules, synthetic records and a time zone to cover before, at and after the deadline.
Using Claude where available: Supply test-model parameters, dependencies and saving steps to draft checks for changes and reopening.
Using Claude where available: Supply strategy versions, opponents, random seeds and scoring rules to design a consistent evaluation.
Using Claude where available: Supply fictional players, rooms and event logs to draft checks for delayed messages, duplicate subscriptions and cross-room delivery.
Using Claude where available: Supply completion rules, synthetic state logs and the agent’s claim to separate completion, progress and unverified outcomes.
Using Claude where available: Supply fictional segments, ticket groups and terms to list each supplier, responsibility and open question.
Using Claude where available: Supply synthetic flight-search and access logs to list completed research, blocked steps and pending human actions.