- Home
- Skills
- Code Quality & Review
- vibe code cleanup
More screenshots
Works with the AI Agents you already use
vibe code cleanup
Systematically audit and refactor AI-generated codebases through phased, behavior-preserving cleanup steps.
$9.99
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
vibe code cleanup
Example session with this skill installed
My AI-built React app is a mess and I can't add new features without breaking things. Can you audit the code and clean it up?
- Read your context and instructions
- Compiled the vibe code cleanup
- Generated the document
I have completed the reconnaissance and initial audit of the repository. The project is a Next.js application with several instances of redundant state logic and inconsistent styling patterns typical of AI-generated code.
Audit Report: AI-Generated Smells
| Location | Severity | Smell Type | Recommended Fix |
|---|---|---|---|
src/components/UserDashboard.tsx | Critical | Duplicate State Sync | Consolidate 3 useEffect hooks into a single state transition. |
package.json | Major | Hallucinated Deps | Remove react-query-v5-adapter (non-existent package). |
src/lib/api.ts | Major | Hardcoded Secrets | Move OPENAI_API_KEY from code to .env.local. |
src/hooks/useAuth.ts | Minor | Verbose Logic | Refactor 45-line switch statement into a lookup object. |
styles/globals.css | Minor | CSS Redundancy | Remove 12 unused utility classes generated by repetitive prompting. |
Executive Summary: The codebase is functional but fragile. The primary issues are duplicate logic in the dashboard and security risks involving hardcoded keys. Fixing these will reduce the build error count from 14 to 0.
Proposed Cleanup Phases:
- Phase 1: Security & Hygiene: Move secrets to environment variables and remove dead dependencies.
- Phase 2: Logic Consolidation: Refactor the dashboard state management to prevent race conditions.
- Phase 3: Type Safety: Resolve the 14 TypeScript errors in the auth and API layers.
Next steps
- Approve the three cleanup phases listed above.
- Confirm if the
react-query-v5-adapterwas intended for a specific internal tool. - Provide the
.env.examplevalues for the hardcoded secrets.
UserDashboard.tsx
PDF · document
Example file from a real run - the skill writes it into your workspace.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Inheriting a codebase built entirely by LLMs often means dealing with a "vibe-coded" mess of inconsistent patterns, dead code, and fragile logic. This skill provides a systematic framework for developers to audit, plan, and execute a behavior-preserving cleanup of AI-generated projects. It moves beyond simple linting by identifying specific "AI smells"—like hallucinated library usage or redundant state logic—and fixing them in verifiable phases.
What it does
- Codebase Reconnaissance maps the stack, dependencies, and file scale to establish a technical baseline.
- AI-Smell Auditing scans for specific patterns typical of AI generation, ranking them by severity from minor to critical.
- Phased Refactoring breaks down the cleanup into hygiene, typing, structure, and state management phases.
- Automated Verification runs builds and typechecks after every phase to ensure no regressions occur.
- Final Guardrails provides a before/after metrics report and recommendations for CI/CD and linting rules.
How it works
- Baseline: Run the existing project to record current type errors, lint warnings, and build status.
- Audit: Generate a severity-ranked report identifying specific AI-generated technical debt.
- Plan: Review the proposed 3-6 phase cleanup plan and approve the scope.
- Execute: The agent performs one phase at a time, verifying the build between each session.
- Finalize: Receive a comparative report showing improved metrics and future maintenance guidelines.
Frameworks & tools
Works with any standard web or backend stack including React, Next.js, Node.js, and Python. It utilizes existing project tooling like TypeScript, ESLint, and Vitest/Jest for verification gates.
Why this beats prompting it yourself
Generic cleanup prompts often lead to massive, breaking changes that are impossible to debug. This skill enforces a strict "one phase, one verification" rule and uses a specialized catalog of AI-specific code smells that general-purpose prompts usually miss.
Use cases
- MVP Handover: Cleaning up a prototype built with AI before hiring a full-time engineering team.
- Technical Debt Triage: Fixing a project that has become too buggy to add new features safely.
- Security Hardening: Identifying and removing hardcoded secrets or unsafe patterns left by rapid AI prompting.
Known limitations
Does not perform framework migrations or architectural rewrites. Requires a functional build or test command to establish a baseline.
Requires existing build/test scripts to establish a baseline. Does not support full framework migrations or repo restructuring without explicit user requests.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 11 days ago