desloppify

Detect technical debt and code quality issues across multi-language codebases.

55|14|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/gobifrost/bifrost --skill desloppify-gobifrost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desloppify
Source: https://github.com/gobifrost/bifrost/tree/main/.claude/skills/desloppify
Command: npx skills add https://github.com/gobifrost/bifrost --skill desloppify-gobifrost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually identifying technical debt, code smells, and quality gaps across multi-language codebases is time-consuming, inconsistent, and often misses hidden maintenance risks that slow down development teams and increase long-term maintenance costs.

Core Features & Use Cases

  • Multi-language codebase health scanning: Detects mechanical issues (dead code, unused imports, duplication, security smells) and subjective quality gaps (naming, error handling, abstractions, clarity) across projects.
  • Prioritized cleanup workflow: Automatically triages findings, builds a prioritized execution queue, and guides users through fixes with branch management, commit tracking, and PR integration.
  • Use Case: A team maintaining separate frontend and backend projects can scan each codebase individually to avoid mixed scan state, get a ranked list of fixes, and execute cleanup work on a dedicated branch without disrupting main development.

Quick Start

Use the desloppify skill to run a full health scan of your current codebase and get a prioritized list of cleanup tasks to improve code quality.

Frequently Asked Questions about desloppify

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

FAQPage Schema
How do I scan a multi-language monorepo for technical debt and code smells?

To scan a multi-language monorepo for technical debt, you can run an automated health scan that detects dead code, unused imports, duplication, and security smells across all projects. The scanner triages findings and builds a prioritized execution queue for cleanup.

What is the best way to prioritize code cleanup tasks across separate frontend and backend projects?

The best way to prioritize code cleanup tasks is to scan each codebase individually to avoid mixed scan state, which generates a ranked list of fixes. This automated triage builds a prioritized execution queue to guide teams through code health improvements.

Can I manage technical debt remediation on a dedicated branch without disrupting main development?

Yes, you can manage technical debt remediation on a dedicated branch without disrupting main development. The workflow guides users through fixes with branch management, commit tracking, and PR integration to safely execute cleanup work.

Does automated code health scanning detect subjective quality gaps like poor naming and abstractions?

Automated code health scanning does detect subjective quality gaps like poor naming, error handling, abstractions, and clarity issues. It evaluates both mechanical issues and subjective quality gaps to maximize strict code health scores.

What types of maintenance risks can a codebase cleanup automation tool identify?

A codebase cleanup automation tool identifies maintenance risks such as dead code, unused imports, code duplication, and security smells. It also detects subjective quality gaps including naming inconsistencies, poor error handling, and unclear abstractions.

How do I track and execute a prioritized queue of refactoring tasks for code health improvement?

To track and execute a prioritized queue of refactoring tasks, the system automatically triages findings and guides users through fixes using branch management, commit tracking, and PR integration. This ensures structured code health improvement.