AI Prompts for Coding

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Turn [bug report] and [observed behavior] into a reproducible case, missing questions, and measurable acceptance criteria. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check every criterion against the reported symptom; separate facts from assumptions. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Inspect [files] for [requested change]; map callers, dependencies, and the smallest files that need edits. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Identify affected public contracts and one regression check for each. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Extract [repeated calculation] into one helper while preserving rounding, exceptions, and call order. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Compare old and proposed outputs on boundaries and invalid inputs. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Divide [function] into named steps without changing side effects, return values, or error order. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Trace one successful and one failing path before and after. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Rename [variable] consistently across [scope], including callers, fixtures, and serialized uses where applicable. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. List references that must stay unchanged for compatibility. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Explain and name [numeric literals] in [code] using [domain requirements]; avoid inventing meanings. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check boundary conditions and configuration overrides. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Assess [suspected dead branch] using supplied callers and conditions before proposing its removal. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Show reachability reasoning and flag paths not covered by supplied evidence. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Refactor [internal implementation] while retaining [public signatures], errors, and response shape. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Define contract comparisons for existing consumers. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Add a small seam around [external dependency] so [component] can be tested without network access. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify production wiring and a representative failure response. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Split [mixed function] into input parsing and domain logic with explicit validation boundaries. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Test malformed input separately from valid but rejected domain cases. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Simplify [null-checking code] while preserving distinctions among missing, null, false, zero, and empty values. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Enumerate those cases and compare behavior. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Review [shared object usage] and propose a clear ownership contract before changing mutation behavior. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Trace all writers and a nested-call scenario. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Gate [new behavior] behind [configuration mechanism] with a documented default and rollback path. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify both switch states and missing configuration behavior. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [provided migration notes] to replace [deprecated call] with the smallest compatible update. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check signatures, defaults, and changed error semantics against supplied notes. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Implement [requested improvement] under [allowed files] and [change limits]; identify necessary exceptions first. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Review the diff for unrelated formatting and behavior changes. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [current implementations] and [proposed abstraction] for shared rules and meaningful differences. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Demonstrate one case the abstraction simplifies and one it must preserve separately. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Normalize [input field] once at [system boundary] with explicit whitespace, case, and locale rules. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Compare raw, normalized, invalid, and round-trip values. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Map [module cycle] and move only the smallest shared contract needed to break it. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check import order and public exports without adding a new cycle. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Clarify precedence among [defaults], [file settings], [environment values], and [runtime overrides]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Build a precedence table including explicitly empty values. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [patch] with [requested behavior]; mark necessary changes, unrelated edits, and missing acceptance cases. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Tie each proposed edit to a specific requirement. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [minimal reproducer] to design a test that fails for the reported defect and passes after the smallest fix. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. State the assertion that distinguishes failure from success. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Create a compact boundary matrix for [numeric rule], including precision, limits, and invalid values. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Explain why each case catches a distinct defect. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Create checks for [API response contract] covering status, required fields, nullability, and compatibility. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify optional fields do not become accidental requirements. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Replace wall-clock dependence in [test] with [available clock seam] and explicit timestamps. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check midnight, elapsed-time boundaries, and timezone assumptions. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Make [randomized tests] reproducible using explicit seeds and isolated random generators. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check that a reported failure can be replayed with its seed. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Analyze [test code] and [failure logs] for races, premature assertions, and leaked work. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Propose event-based synchronization and a repeatable failure scenario. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design checks for [write endpoint] using repeated requests and [idempotency requirements]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify duplicate calls, conflicting payloads, and failed first attempts. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Build only the fixture rows required for [behavior], with explicit relationships and teardown. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check independence from preexisting data and test order. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Specify properties for [transformation] such as invariants, round trips, or monotonicity where justified. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Include counterexamples and avoid assuming invalid mathematical properties. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Convert [duplicated tests] into a readable parameter table without losing distinct assertions. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check case names explain expected behavior when a row fails. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design a cancellation test for [operation] at [supported cancellation points]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify cleanup, partial side effects, and final reported state. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Test [resource-owning code] when acquisition, processing, or disposal fails. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check release happens exactly as required and original errors remain observable. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Classify checks for [component] by dependencies and the uncertainty each check resolves. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Identify what mocked tests cannot prove about the target system. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [mock] with [dependency contract] and revise only behavior that hides real failures. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check return types, timing, errors, and call counts. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Draft a test plan for [migration] and [rollback policy] using a disposable database. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify data preservation and specify irreversible steps honestly. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Create cases for [roles], [resources], and [allowed actions] from [policy]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check denied operations as well as successful operations. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Validate [generated file] using meaningful structure and content assertions. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Exclude volatile metadata while checking user-important layout or fields. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Review [surviving mutations] and identify missing meaningful assertions or equivalent mutations. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Explain each proposed test's observable failure condition. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Summarize [actual test logs] with environment, executed checks, failures, and unexecuted checks. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Do not turn planned or inferred checks into passed results. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Analyze [tests] for shared globals, fixtures, caches, or environment leakage and isolate the minimum state. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify representative reversed-order and individual runs where execution is available. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [crash report], [stack trace], and [input] to isolate the smallest failing path. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Distinguish reproduced evidence from suspected causes. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Follow [field] through [code path] to locate where a valid value is lost or overwritten. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check missing, null, false, and asynchronous update cases. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [local configuration] and [sanitized production diagnostics] for relevant differences. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Propose one change at a time and avoid exposing secrets. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Analyze [timing logs] and [request path] to separate queueing, connection, processing, and retry delays. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Identify measurable evidence needed for each suspected stage. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [heap snapshots] and [allocation timeline] to locate growing retained objects. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Differentiate normal caching from unbounded retention. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Correlate [request logs], retries, and [write code] to identify duplicate side effects. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check request identity and the transaction boundary. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Analyze [timestamp samples] and [date handling code] for timezone conversion or calendar-boundary errors. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Compare UTC, local dates, daylight transitions, and offsets supplied by the user. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [page-size rule], [dataset size], and [pagination code] to locate skipped or duplicated items. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check empty, exact-multiple, final partial, and first-page cases. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Trace [cache keys], [write flow], and [stale response] to locate missing invalidation or key mismatch. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check mutation success, deletion, and cache expiration paths. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Add narrow handling for [malformed response example] at [integration boundary]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Verify valid responses retain their original behavior. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.