skills.rest
anthony-spruyt
anthony-spruytCOMMUNITY
Explore all skills by this author →
GitHub

desloppify

Scan codebases to detect technical debt, dead code, and code smells.

3|Updated Jan 13, 2026
Search Tags:#code quality#code analysis#refactoring#maintainability#technical debt#code scanning
One-click install
npx skills add https://github.com/anthony-spruyt/xfg --skill desloppify-anthony-spruyt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desloppify
Source: https://github.com/anthony-spruyt/xfg/tree/main/.claude/skills/desloppify
Command: npx skills add https://github.com/anthony-spruyt/xfg --skill desloppify-anthony-spruyt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining high code quality and managing technical debt by providing automated scanning, analysis, and actionable insights for code improvement.

Core Features & Use Cases

  • Codebase Scanning: Analyzes code for quality issues, technical debt, dead code, large files, code smells, and more across 28 languages.
  • Technical Debt Tracking: Identifies and prioritizes issues to fix, tracks progress through scoring, and helps create cleanup plans.
  • Automated & Manual Reviews: Supports automated subjective reviews and provides clear instructions for manual assessments.
  • Use Case: A development team can use this Skill to regularly scan their project, identify the most critical issues impacting performance and maintainability, and systematically address them to improve the overall health score of their codebase.

Quick Start

Run the desloppify next command to identify the next issue to fix in the codebase.

Frequently Asked Questions about desloppify

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

FAQPage Schema
How do I track technical debt and identify areas for code refactoring?▼

Technical debt tracking and refactoring identification are achieved by scanning your codebase to detect code smells, dead code, and large files, then prioritizing these issues to create a systematic cleanup plan.

Can I scan for code smells and dead code across multiple programming languages?▼

Code smell and dead code scanning supports 28 multiple programming languages, analyzing file sizes and dependency issues to provide actionable insights for overall codebase maintainability.

What is the best way to automate subjective code reviews for maintainability?▼

Automated subjective code reviews for maintainability are supported by scanning codebase health, generating scores, and providing clear instructions for manual assessments to enhance developer productivity.

How do I start analyzing codebase health to improve code quality?▼

Codebase health analysis starts by running the next command, which identifies the most critical issue to fix, calculates a health score, and provides actionable insights for code improvement.

Does this code analysis tool work with dependency issues and large file detection?▼

Dependency issue and large file detection work across 28 languages, analyzing codebase health to pinpoint performance impacts and maintainability risks for technical debt reduction.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
santosomarsantosomar
1

technical-debt-analyzer

Analyze codebases to quantify and prioritize technical debt hotspots.

Community
Intermediate
CyapstayeCyapstaye
9

requesting-code-review

Scan staged diffs for security vulnerabilities and logic errors before commit.

Community
Advanced
voidrotvoidrot

sast-configuration

Configure SAST tools like Semgrep, CodeQL, and SonarQube for CI/CD pipelines.

Community
Intermediate