Python Code Checker

Problem It Addresses

When Python learners, instructors, or interview candidates review code, a submission can run yet still miss hidden requirements: empty inputs, boundary cases, duplicates, casing, output formatting, or constraints. Python Code Checker focuses on that specific workflow: evaluating a pair of problem statement and submitted code, rather than giving generic style advice.

How It Works

It follows an explainable sequence: establish intent, verify correctness, explain issues line by line, and then assess whether a better implementation exists.
- Understand the problem: extract inputs, outputs, constraints, and implicit conditions; if the prompt is ambiguous, it asks for clarification before judging.
- Check correctness: by running the code or simulating execution paths, it inspects syntax, logic coverage, boundary handling, and output format.
- Correct line by line: passing lines can be skipped or briefly noted, while syntax errors, logic mistakes, and missing edge cases are called out with beginner-friendly explanations.
- Compare optimizations: if a solution with lower time or space complexity, cleaner structure, or more Pythonic use of built-ins exists, it provides the alternative and explains the trade-offs; if the original is already near optimal, it says so.

Boundaries

This skill is best suited to practice problems, coursework, and handwritten interview code reviews. It is not a replacement for flake8, mypy, pytest, or security auditing. When the prompt is incomplete or input ranges are undefined, conclusions depend on the clarification supplied. Performance comments focus on complexity, readability, and sensible use of Python built-ins.