vibe-code-cleanup
Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.). Removes dead imports, unused files, and broken references without breaking routes or APIs.
Profile →npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Vibe-Code Cleanup — Production Refactor Skill A safe, incremental cleanup workflow for AI-generated / vibe-coded fullstack apps. The goal is to make the codebase production-ready **without** breaking anything that already works. ## When to Use - Use when a rapidly built app works but has broken imports, duplicated logic, dead code, unclear environment variables, or fragile release hygiene. - Use before launch or handoff to convert exploratory code into a maintainable production baseline. - Use when cleanup must preserve existing behavior and avoid broad rewrites of routes, APIs, auth, data models, or integrations. ## Core Philosophy > **Surgery, not demolition.** Remove only what is provably dead. Preserve everything else. Never: - Rewrite working systems for cosmetic reasons - Rename routes, slugs, or API endpoints that may be indexed or cached - Change tool inputs/outputs, API contracts, DB schema, or auth flow - Delete files you haven't verified are unused - Make broad sweeping changes in a single commit Always: - Make small, targeted, reversible changes - Validate after every meaningful batch of changes - Prefer shared helpers over copy-pasted blocks - Keep backward compatibi
- When to Use
- Core Philosophy
- Step 1 — Reconnaissance (read before touching)
- Step 2 — Fix Broken Imports First
- Step 3 — Identify Dead Code (verify before removing)
- Step 4 — Consolidate Repeated Logic into Helpers
- Step 5 — Environment Variable Audit
- Step 6 — Validate After Every Batch
- Step 7 — Commit Strategy
- What NOT to Clean Up
- Cleanup Checklist
- Limitations
List all pages/routes
find . -type f \( -name 'page.js' -o -name 'page.jsx' -o -name 'page.ts' -o -name 'page.tsx' \)
find pages -type f \( -name '*.js' -o -name '*.jsx' -o -name '*.ts' -o -name '*.tsx' \) | rg -v '/_' | sort
Find broken imports (TS projects)
npx tsc --noEmit 2>&1 | head -80
Find unused exports (optional, for larger projects)
npx ts-prune 2>/dev/null | head -40
Check for console.log / debug leftovers
grep -r "console\.log\|debugger\|TODO\|FIXME\|HACK" --include="*.{js,ts,jsx,tsx}" -l
npx tsc --noEmit 2>&1What does the vibe-code-cleanup skill do?
Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.). Removes dead imports, unused files, and broken references without breaking routes or APIs.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.