skills.rest
Ven0m0
Ven0m0COMMUNITY
Explore all skills by this author →
WebsiteGitHub

bloat-detector

Detect and quantify codebase bloat across dead code, duplication, complexity, and documentation.

6|1|Updated Jan 21, 2026
Search Tags:#code quality#static analysis#optimization#technical debt#cleanup#bloat
One-click install
npx skills add https://github.com/Ven0m0/claude-config --skill bloat-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bloat-detector
Source: https://github.com/Ven0m0/claude-config/tree/main/plugins/conserve/skills/bloat-detector
Command: npx skills add https://github.com/Ven0m0/claude-config --skill bloat-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Grep, Glob, Read, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically identifies and helps remove various forms of code bloat, including dead code, duplication, complexity, and documentation issues, leading to a cleaner, more efficient codebase.

Core Features & Use Cases

  • Progressive Analysis: Offers multiple tiers of analysis, from quick scans to deep audits.
  • Bloat Categories: Detects code, AI-generated, documentation, dependency, and git history bloat.
  • Use Case: Before a major refactoring effort, run a deep audit using /bloat-scan --level 3 to identify all areas of technical debt and prioritize cleanup tasks based on token savings and maintenance impact.

Quick Start

Run a quick scan to detect common bloat patterns in your codebase.

Frequently Asked Questions about bloat-detector

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

FAQPage Schema
How do I detect dead code and technical debt in my codebase?▼

AI-generated artifacts are flagged as a distinct bloat category during deep static analysis. The scanner detects redundant or low-value AI-generated code patterns and suggests appropriate remediation actions like DELETE or REFACTOR to eliminate technical debt.

What is the best way to scan for code duplication before a major refactoring effort?▼

Analysis tiers range from quick heuristic scans to deep static analysis and git history examination. You can start with a quick scan to detect common bloat patterns and progressively move to deeper audits for comprehensive technical debt identification.

Can I use Bash and Grep to identify code complexity and documentation bloat?▼

Yes, the analysis leverages Bash, Grep, Glob, and Read dependencies to systematically identify code complexity and documentation bloat. It scans the codebase to quantify these issues and provides actionable remediation steps like CONSOLIDATE or ARCHIVE.

When should I run a deep static analysis audit instead of a quick bloat scan?▼

You should run a deep static analysis audit instead of a quick scan before major refactoring efforts or when you need to identify all areas of technical debt. Use quick scans for routine checks and deep audits for comprehensive cleanup prioritization based on token savings.

Related Skills

Explore More Software Engineering Skills→
iiammaeiiammae

differential-review

Automate security-focused code review of diffs and generate markdown reports.

Community
Advanced
anserIndicusanserIndicus

openclaw-cost-guard

Inspect AI run data to identify token and cost waste sources.

Community
Advanced
cuenobicuenobi

sonarqube-quality-gate

Analyze code changes against SonarQube rules for quality gate compliance.

Community
Intermediate
smileynetsmileynet

code-pruning

Detect and remove dead code, unused dependencies, and codebase bloat.

Community
Intermediate