codebase-auditlisted

# Pre-Push Codebase Audit As a senior engineer, you're doing the final review before pushing this code to GitHub. Check everything carefully and fix problems as you find them. ## When to Use This Skill - User requests "audit the codebase" - Before making the first push to GitHub - Before making a repository public - Pre-production deployment review - User asks to "clean up the code" or "optimize everything" ## Your Job Review the entire codebase file by file. Read the code carefully. Fix issues right away. Don't just note problems—make the necessary changes. ## Audit Process ### 1. Clean Up Junk Files Start by looking for files that shouldn't be on GitHub: **Delete these immediately:** - OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini` - Logs: `*.log`, `npm-debug.log*`, `yarn-error.log*` - Temp files: `*.tmp`, `*.temp`, `*.cache`, `*.swp` - Build output: `dist/`, `build/`, `.next/`, `out/`, `.cache/` - Dependencies: `node_modules/`, `vendor/`, `__pycache__/`, `*.pyc` - IDE files: `.idea/`, `.vscode/` (ask user first), `*.iml`, `.project` - Backup files: `*.bak`, `*_old.*`, `*_backup.*`, `*_copy.*` - Test artifacts: `coverage/`, `.nyc_output/`, `test-results/` - Personal junk: `TODO.txt`, `NOTES.txt`, `scratch.*`, `test123.*` **Critical - Check for secrets:** - `.env` files (should never be committed) - Files containing: `password`, `api_key`, `token`, `secret`, `private_key` - `*.pem`, `*.key`, `*.cert`, `credentials.