vibe-audit

Name: vibe-audit
Availability: InStock
Author: izmailovilya

Identify dead or experimental code and generate a structured cleanup report.

41|10|Updated Jan 21, 2026

Search Tags:#codebase #audit #refactor #dead-code #code-cleanup #interactive-review #feature-audit

Ready to run

npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill vibe-audit-izmailovilya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-audit
Source: https://github.com/izmailovilya/ilia-izmailov-plugins/tree/main/plugins/vibe-audit/skills/vibe-audit
Command: npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill vibe-audit-izmailovilya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify potentially dead or experimental code and ask the user whether it's still needed.

Core Features & Use Cases

Discovery of dead/experimental features in a codebase.
Guided interactive review where each item is queried individually.
Generate a structured cleanup report and action plan for code cleanup.

Quick Start

Scan your codebase and begin the interactive review to decide which items to keep, remove, or deprecate.

Frequently Asked Questions about vibe-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find dead code in my codebase?▼

Finding dead code involves scanning your codebase to identify potentially unused or experimental features. You can apply the audit to specific scopes like server, UI, stores, or the full repository to flag items for review and generate a cleanup plan.

What is an interactive code audit?▼

An interactive code audit is a guided review process where each potentially dead or experimental code item is queried individually. You decide the fate of each flagged item step-by-step, ensuring controlled code cleanup rather than automated deletion.

How do I create a code cleanup action plan?▼

A code cleanup action plan is generated after an interactive review of dead code. By deciding the fate of each flagged item individually, the audit outputs a structured remediation report detailing what to remove, keep, or deprecate across your features.

Can I scope a dead code audit to specific features or UI?▼

Yes, you can scope a dead code audit to specific features, server, UI, stores, or the full repository. This targeted scanning ensures the interactive review and resulting cleanup report focus only on the codebase areas you specify.

What is the best way to remove experimental code from a repository?▼

The best way to remove experimental code is using an interactive audit that prompts you to decide its fate item by item. This step-by-step workflow prevents accidental deletion of needed code and produces a structured remediation report for cleanup.