make-publiclisted

# /make-public Run a safety checklist on the current repository to verify it's ready to be made public. ## The only hard blockers for going public are: 1. **Secrets/credentials** in tracked files or git history 2. **Hardcoded personal paths** with PII (e.g. absolute user paths, email addresses, full names in unexpected places) Being messy, having personal style, or having rough edges is NOT a blocker. ## Checklist to Run ### 1. Secret Scan (CRITICAL) Search tracked files for patterns that look like secrets: - API keys: `sk-`, `Bearer `, `_SECRET`, `_TOKEN`, `_KEY`, `_PASSWORD`, `api_key`, `apikey` - Personal: email addresses matching `@`, hardcoded user paths (e.g. `C:\Users\username\`), personal IP addresses - Auth: `Authorization:`, `password =`, `token =`, `.env` files tracked in git Run: `git grep -i "api_key\|secret\|password\|token\|bearer" -- "*.py" "*.js" "*.json" "*.env" "*.cfg" "*.ini" 2>/dev/null | head -20` Also check: `git ls-files | grep -i "\.env\|secret\|credential\|auth\|token"` ### 2. Gitignore Check - Does `.gitignore` exist? - Does it cover: `*.env`, `*.log`, `data/`, `node_modules/`, `__pycache__/`, `*.pyc`, build outputs? - Are any sensitive files currently tracked that should be ignored? Run: `git ls-files | grep -E "\.env$|\.log$|token|secret|credential" | head -10` ### 3. README Check - Does README.md exist? - Does it explain what the project does? (Even a one-liner is fine) - Does it have any setup/usage instructions? ### 4. Recent Commits