Agent skill

Vibe Code Cleanup

by sickn33 in sickn33/agentic-awesome-skills

Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.).

MITAuto-check: notes

Install Vibe Code Cleanup

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills vibe-code-cleanup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vibe-code-cleanup .claude/skills/vibe-code-cleanup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-code-cleanup
GitHub stars
47k
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
559 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.).

  • Works in 7 steps: Reconnaissance (read before touching) → Fix Broken Imports First → Identify Dead Code (verify before… → …
  • SKILL.md covers When to Use, Core Philosophy, Step 1 — Reconnaissance (read… and Step 2 — Fix Broken Imports…, plus 8 more sections
  • Calls npx, npm and rg

What it does

Vibe Code Cleanup is an agent skill from sickn33/agentic-awesome-skills. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Next.js, React and Node.js. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

Example prompts

  • “/vibe-code-cleanup”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Reconnaissance (read before touching)
  2. Fix Broken Imports First
  3. Identify Dead Code (verify before removing)
  4. Consolidate Repeated Logic into Helpers
  5. Environment Variable Audit
  6. Validate After Every Batch
  7. Commit Strategy

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • npm
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Code Cleanup loads about 1.8k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 559 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:154
    # Compare against .env.example or .env.local
  • NoteMentions a .env fileSKILL.md:155
    cat .env.example 2>/dev/null || cat .env.local 2>/dev/null

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 559 words, ~1,753 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-code-cleanup/SKILL.md (or your agent's skills folder).
name
vibe-code-cleanup
description
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.
category
fullstack
risk
safe
source
self
source_type
self
date_added
2026-05-31
author
Whoisabhishekadhikari
tags
cleanup, refactor, nextjs, production, vibe-code, fullstack, nodejs
tools
claude, cursor, gemini, claude-code
version
1.0.0

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 compatibility

Step 1 — Reconnaissance (read before touching)

Before changing anything, map the codebase:

bash
# 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

Document what you find. Do NOT change yet.


Step 2 — Fix Broken Imports First

Broken imports cause build failures and should be fixed before anything else.

bash
# TypeScript: list all errors
npx tsc --noEmit 2>&1

# Common patterns to fix:
# - Missing file (file was deleted or renamed)
# - Wrong relative path (../lib vs ../../lib)
# - Named export that doesn't exist

Fix rule: Fix the import reference. Do NOT delete the referenced file unless you've confirmed it's unused everywhere.


Step 3 — Identify Dead Code (verify before removing)

A file/export is safe to remove only if:

  1. No other file imports it (grep-confirmed)
  2. It's not referenced in config, sitemap, or route manifest
  3. It's not a public-facing URL (page.js, route.js)
bash
# Check if a file is imported anywhere
grep -r "from.*my-file\|require.*my-file" --include="*.{js,ts,jsx,tsx}" .

# Check if a component is used anywhere  
grep -r "MyComponent" --include="*.{js,ts,jsx,tsx}" .

Step 4 — Consolidate Repeated Logic into Helpers

Look for repeated patterns (metadata blocks, API fetch wrappers, error handlers) that appear in 3+ places.

Good consolidation targets:

  • Page-level SEO metadata (Open Graph, Twitter cards, canonical)
  • Fetch wrappers with error handling
  • Repeated utility functions (slugify, formatDate, truncate)

Bad consolidation targets (leave alone):

  • One-off business logic
  • Route handlers with different contracts
  • Anything touching DB schema or auth

Pattern for shared metadata helper (Next.js):

js
// lib/socialMetadata.js
export function buildPageMetadata({ title, description, path, image }) {
  const baseUrl = process.env.NEXT_PUBLIC_BASE_URL || 'https://yourdomain.com';
  const imageUrl = image?.startsWith('http') ? image : `${baseUrl}${image}`;
  
  return {
    title,
    description,
    openGraph: {
      title,
      description,
      url: `${baseUrl}${path}`,
      images: [{ url: imageUrl, width: 1200, height: 630, alt: title }],
    },
    twitter: {
      card: 'summary_large_image',
      title,
      description,
      images: [imageUrl],
    },
    alternates: {
      canonical: `${baseUrl}${path}`,
    },
  };
}

Show full SKILL.md (225 more words)Show less

Step 5 — Environment Variable Audit

bash
# List all env vars used in code
grep -r "process\.env\." --include="*.{js,ts,jsx,tsx}" . | grep -oP 'process\.env\.\w+' | sort -u

# Compare against .env.example or .env.local
cat .env.example 2>/dev/null || cat .env.local 2>/dev/null

Flag any env vars used in code but missing from .env.example. Never add secrets to version control.


Step 6 — Validate After Every Batch

Run this after every meaningful batch of cleanup changes:

bash
# TypeScript check
npx tsc --noEmit

# Lint
npx eslint . --ext .js,.jsx,.ts,.tsx --max-warnings 0

# Build (catches runtime issues TypeScript misses)
npm run build

# Tests (if present)
npm test -- --runInBand --passWithNoTests

If build or typecheck breaks → revert the last batch before continuing.


Step 7 — Commit Strategy

Each commit should be a single logical unit:

text
fix: remove broken import in app/blog/page.js
refactor: consolidate social metadata into lib/socialMetadata.js  
chore: remove verified-unused utils/oldHelper.js
fix: standardize env var references to NEXT_PUBLIC_BASE_URL

Never bundle UI changes + logic changes + file deletions in one commit. Smaller commits = easier rollback.


What NOT to Clean Up

Treat these as off-limits unless there's a verified bug:

AreaWhy
Route slugs / page pathsMay be indexed by Google
API route contractsCallers depend on exact shape
DB schema / Prisma modelsMigration required
Auth flow logicSecurity-sensitive
Third-party integration configsKeys/webhooks are environment-specific
Working tool pagesUser-facing functionality

Cleanup Checklist

  • TypeScript errors fixed
  • No broken imports
  • Dead code removed (grep-verified)
  • Shared helpers created for repeated patterns (3+ uses)
  • No hardcoded secrets or local-only URLs
  • All env vars documented in .env.example
  • Build passes
  • Tests pass (or no tests exist)
  • Lint passes
  • Each commit is scoped and explainable

Limitations

  • Does not infer product intent from code alone; confirm behavior before deleting routes, components, API contracts, or data models.
  • Cleanup should be applied in small reviewed batches because broad refactors can hide regressions.
  • Avoid changing auth, billing, persistence, or third-party integration behavior without explicit requirements and tests.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/vibe-code-cleanup of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Vibe Code Cleanup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Code Cleanup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Code Cleanup this skillsickn33/agentic-awesome-skills47k1 repos~1.8kAutomated safety check: NotesMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0
Core Web VitalsvmDeshpande/ai-agent-automation1784 repos~3.6kAutomated safety check: PassMIT
Senior QAnicepkg/auto-company1923 repos~1.1kAutomated safety check: NotesNone
Accessibility CompliancevmDeshpande/ai-agent-automation1783 repos~601Automated safety check: PassApache-2.0
Databuddydatabuddy-analytics/Databuddy1.2k—~2.1kAutomated safety check: PassAGPL-3.0

Similar skills

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Core Web Vitals

    vmDeshpande/ai-agent-automation

    Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking.

    178 GitHub starsUsed in 4 repos~3.6k tokens
    Frontend & DesignAuto-check passed
  • Senior QA

    nicepkg/auto-company

    Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.

    192 GitHub starsUsed in 3 repos~1.1k tokens
    Testing & QAAuto-check: notes
  • Accessibility Compliance

    vmDeshpande/ai-agent-automation

    Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support.

    178 GitHub starsUsed in 3 repos~601 tokens
    Frontend & DesignAuto-check passed
  • Databuddy

    databuddy-analytics/Databuddy

    Integrate Databuddy analytics using the SDK, REST API, or MCP.

    1.2k GitHub stars~2.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • PR Review

    cdklabs/cdk-nextjs

    Review the current PR branch and fix the findings in rounds until reviews come back clean.

    111 GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Vibe Code Cleanup

What does Vibe Code Cleanup do?

Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.). Vibe Code Cleanup is an agent skill from sickn33/agentic-awesome-skills.).

How do I install Vibe Code Cleanup in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup -a claude-code`. Or copy the skill folder (skills/vibe-code-cleanup in sickn33/agentic-awesome-skills) into .claude/skills/vibe-code-cleanup in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Code Cleanup in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup -a codex`. Or copy the skill folder (skills/vibe-code-cleanup in sickn33/agentic-awesome-skills) into .agents/skills/vibe-code-cleanup in your project. Codex loads it when a task matches its description.

Can I use Vibe Code Cleanup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill vibe-code-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-code-cleanup, .gemini/skills/vibe-code-cleanup, .github/skills/vibe-code-cleanup and .opencode/skills/vibe-code-cleanup in your project.

What does Vibe Code Cleanup need to run?

Going by SKILL.md and its folder, Vibe Code Cleanup needs the command-line tools its instructions call (npx, npm and rg). Our summary lists: Node.js.

Does Vibe Code Cleanup access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vibe Code Cleanup safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vibe Code Cleanup use?

Vibe Code Cleanup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Code Cleanup use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Code Cleanup?

Skills that share tags, products or a category with Vibe Code Cleanup: Wcag Audit Patterns (vmDeshpande/ai-agent-automation, 178 stars), Core Web Vitals (vmDeshpande/ai-agent-automation, 178 stars), Senior QA (nicepkg/auto-company, 192 stars) and Accessibility Compliance (vmDeshpande/ai-agent-automation, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Code Cleanup?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.