Edge Case Logic Auditor

Edge Case Logic Auditor is built for code that looks correct at first glance but fails on unusual inputs. It asks the model to inspect conditions, branches, loops, and boundary values for hidden bugs. This is especially valuable when a function handles dates, pagination, empty collections, null values, or off-by-one ranges. Instead of focusing only on obvious syntax issues, the prompt pushes the model to search for rare but expensive failures.

The template is ideal for senior engineers, QA-minded developers, and reviewers working on user-facing logic or critical calculations. It emphasizes boundary testing, invalid inputs, and state transitions. The output helps you understand which cases are safe, which are suspicious, and which should be turned into tests immediately. This makes it useful during refactors, bug hunts, and pre-release audits where confidence matters more than speed.

Customize it by pasting the code into {{CODE_BLOCK}}, describing expected behavior in {{EXPECTED_BEHAVIOR}}, and listing known tricky inputs in {{EDGE_CASES}}. If the function is part of a larger workflow, include that context in {{SYSTEM_CONTEXT}} so the model can reason about dependencies. The answer should include an audit summary, a table of risky branches, and concrete test cases. Use this logic audit prompt when you want the model to think like a skeptical tester.