Review this change as a senior engineer. Prioritize correctness, security, data loss, concurrency, and backwards compatibility. Cite exact lines, explain impact, and propose the smallest safe fix. Do not comment on style unless it affects maintainability.
Diagnose this failure using only the evidence provided. Separate observations, hypotheses, and tests. Rank hypotheses by likelihood, propose the cheapest discriminating test, then provide a minimal fix after the root cause is established.
Create a test plan for this code. Cover happy paths, boundaries, failure modes, state transitions, concurrency, and regression risks. Prefer observable behavior over implementation details. Return test names, setup, action, and expected result.
Refactor this code without changing externally observable behavior. First list invariants and public contracts. Then propose small reversible steps, identify regression risks, and supply tests that prove behavior is preserved.
Design a parameterized SQL query for the requirement and schema below. State the target dialect, assumptions, indexes that affect the plan, transaction boundaries, and expected result shape. Flag injection, locking, null, timezone, and pagination risks. Do not invent columns that are not in the schema.
Review this Python code for correctness first, then typing, resource handling, exception boundaries, async behavior, and Python-specific maintainability. Distinguish runtime bugs from optional style improvements. Return a minimal patch and pytest cases for every behavioral change.
Audit this React component for stale closures, effect dependency errors, race conditions, unnecessary state, unstable identities, hydration issues, and accessibility regressions. Explain the user-visible impact of each finding and provide the smallest behavior-preserving fix.
Turn this requested change into a low-risk Git plan. Identify the files and contracts likely affected, propose small reviewable commits, list validation after each commit, and describe a safe rollback. Do not suggest rewriting shared history unless it is explicitly allowed.
Review this system design against its stated scale and reliability requirements. Map data flow, state ownership, failure domains, consistency choices, security boundaries, observability, cost drivers, and operational recovery. Separate required changes from future optimizations and make every trade-off explicit.