Over the past few days, I built and launched Pygame Code Inspector, an automated static analysis web app that checks Pygame scripts for common bugs, bad practices, and performance bottlenecks—all without needing to run the code. Using Python’s built-in ast (Abstract Syntax Tree) module, the backend parses source code in real time to catch missing setup/teardown calls (pygame.init() / pygame.quit()), unmonitored game loops, uncapped frame rates, hardcoded resolutions, unused memory assets, and missing error handling. It aggregates these checks into a clean 0–100 health score and assigns an overall letter grade (A through F).Once the core inspector logic was solid, I built an interactive frontend using Streamlit so users can paste their code directly into the browser for instant feedback. After setting up open-source documentation under an MIT License, I pushed the repository to GitHub and deployed it live via Streamlit Cloud. Navigating server-side requirements and case-sensitive imports on Linux was a great learning experience, but seeing the app live on the web and giving instant feedback on real Pygame code made it completely worth it!