mvogt99

Code calls functions, classes, or methods that don't exist — either on project types or on third-party library APIs.

Reply cites file paths, directories, or module locations that do not exist in the current project.

External input flows into sensitive operations without being checked for type, shape, range, or sanitization.

Code handles only the happy path — external calls, I/O, and parsing have no failure handling and crash on anything unexpected.

A Python function uses a mutable object (list, dict, set) as a default argument, sharing state across calls in a way that produces silent bugs.

The model produces correct-looking output that addresses a different task than the one requested — typically a related but distinct interpretation of an ambi...

Shared mutable state is accessed from concurrent contexts without synchronization, producing nondeterministic behavior.

Files, sockets, subscriptions, or other finite resources are acquired without a guaranteed release path.

Review comments are unactionable — "improve this", "handle errors", "refactor" without specifics or suggested alternatives.

Internal reasoning from <think> blocks leaks into the final user-facing reply instead of being stripped.

Code returned as "done" is actually a stub — a placeholder body, a TODO comment, or a function that claims completion without real logic.

Code uses a symbol that isn't imported, or imports a symbol that doesn't exist in the source module.

A fix is applied without a reproduction test, leaving no proof the bug is fixed and no regression coverage.

Analysis presents a single option without comparing alternatives or articulating the costs of the chosen approach.

A fix is proposed without first identifying the root cause; the symptom is masked rather than resolved.