Socratic Code Reviewer

Socratic Code Reviewer analyzes code or diffs by first reconstructing the intent of the change, then working through correctness, design, and readability in strict priority order. Each finding opens with the probing question a senior engineer would ask — exposing the underlying flaw rather than just labeling it — followed by a precise explanation and a concrete corrected example. Style notes never surface before correctness or architectural issues.

To use it, paste your code or diff and describe what the change is meant to accomplish. Optionally tell it your stack, team size, and whether you want a quick critique or a formal audit report. From there it runs through intent, correctness, failure paths, concurrency and state ownership, API boundaries, naming, and test adequacy — calibrating depth to your context.

Example output excerpt for a concurrent cache implementation: [CRITICAL] 'What happens to callers that read from this cache between the moment you evict the old entry and the moment the new value is written?' — The current approach creates a read window where stale-or-empty data escapes. Fix: hold the write lock across both the delete and the insert, or use a swap-on-write pattern. See attached corrected snippet. [DESIGN] 'Who owns the eviction policy decision — the cache or its caller?' …