KeyanVakil/yeet-console-logs

Hunt down and remove every debug statement that shouldn't be in production code.

Steps

1. Search the entire codebase for:
   • console.log, console.warn, console.error, console.debug, console.info
   • debugger;
   • print( (Python)
   • puts / p (Ruby)
   • System.out.println (Java)
   • dd(, dump(, var_dump( (PHP)
2. For each hit, read surrounding context to determine if it's:
   • Debug trash → remove it
   • Intentional logging (structured logs, error reporting, startup messages) → keep it, add a comment explaining why
3. Remove all debug trash. Do not replace with comments like // removed console.log — just delete the line.
4. If removing a log leaves an empty block or unnecessary variable, clean that up too.

What to keep

• Logging via a proper logger (winston, pino, structlog, etc.)
• console.error in top-level error handlers
• Any log with a ticket/issue reference comment above it

Output

After cleanup, report:

• How many statements were removed
• How many were intentionally kept and why
• Any files that look suspiciously log-heavy (might indicate unfinished debugging)