Codebase health scanner and technical debt tracker. Use when the user asks about code quality, technical debt, dead code, large files, god classes, duplicate functions, code smells, naming issues, import cycles, or coupling problems. Also use when asked for a health score, what to fix next, or to create a cleanup plan. Supports 29 languages.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Codebase health scanner and technical debt tracker. Use when the user asks about code quality, technical debt, dead code, large files, god classes, duplicate functions, code smells, naming issues, import cycles, or coupling problems. Also use when asked for a health score, what to fix next, or to create a cleanup plan. Supports 29 languages.
allowed-tools
Bash(desloppify *)
Desloppify
1. Your Job
Maximise the strict score honestly. Your main cycle: scan โ plan โ execute โ rescan. Follow the scan output's INSTRUCTIONS FOR AGENTS โ don't substitute your own analysis.
Don't be lazy. Do large refactors and small detailed fixes with equal energy. If it takes touching 20 files, touch 20 files. If it's a one-line change, make it. No task is too big or too small โ fix things properly, not minimally.
2. The Workflow
Three phases, repeated as a cycle.
Phase 1: Scan and review โ understand the codebase
desloppify scan --path . # analyse the codebase
desloppify status # check scores โ are we at target?
The scan will tell you if subjective dimensions need review. Follow its instructions. To trigger a review manually:
desloppify review --prepare # then follow your runner's review workflow
Phase 2: Plan โ decide what to work on
After reviews, triage stages and plan creation appear in the execution queue surfaced by next. Complete them in order โ tells you what each stage expects in the :
next
--report
desloppify next # shows the next execution workflow step
desloppify plan triage --stage observe --report "themes and root causes..."
desloppify plan triage --stage reflect --report "comparison against completed work..."
desloppify plan triage --stage organize --report "summary of priorities..."
desloppify plan triage --complete --strategy "execution plan..."
For automated triage: desloppify plan triage --run-stages --runner codex (Codex) or --runner claude (Claude). Options: --only-stages, --dry-run, --stage-timeout-seconds.
Then shape the queue. The plan shapes everything next gives you โ next is the execution queue, not the full backlog. Don't skip this step.
desloppify plan # see the living plan details
desloppify plan queue # compact execution queue view
desloppify plan reorder <pat> top # reorder โ what unblocks the most?
desloppify plan cluster create <name> # group related issues to batch-fix
desloppify plan focus <cluster> # scope next to one cluster
desloppify plan skip <pat> # defer โ hide from next
Phase 3: Execute โ grind the queue to completion
Trust the plan and execute. Don't rescan mid-queue โ finish the queue first.
Branch first. Create a dedicated branch โ never commit health work directly to main:
git checkout -b desloppify/code-health # or desloppify/<focus-area>
desloppify config set commit_pr 42 # link a PR for auto-updated descriptions
The loop:
# 1. Get the next item from the execution queue
desloppify next
# 2. Fix the issue in code# 3. Resolve it (next shows the exact command including required attestation)# 4. When you have a logical batch, commit and record
git add <files> && git commit -m "desloppify: fix 3 deferred_import findings"
desloppify plan commit-log record # moves findings uncommitted โ committed, updates PR# 5. Push periodically
git push -u origin desloppify/code-health
# 6. Repeat until the queue is empty
Score may temporarily drop after fixes โ cascade effects are normal, keep going.
If next suggests an auto-fixer, run desloppify autofix <fixer> --dry-run to preview, then apply.
When the queue is clear, go back to Phase 1. New issues will surface, cascades will have resolved, priorities will have shifted. This is the cycle.
3. Reference
Key concepts
Tiers: T1 auto-fix โ T2 quick manual โ T3 judgment call โ T4 major refactor.
Auto-clusters: related findings are auto-grouped in next. Drill in with next --cluster <name>.
Zones: production/script (scored), test/config/generated/vendor (not scored). Fix with zone set.
Wontfix cost: widens the lenientโstrict gap. Challenge past decisions when the gap grows.
Scoring
Overall score = 25% mechanical + 75% subjective.
Mechanical (25%): auto-detected issues โ duplication, dead code, smells, unused imports, security. Fixed by changing code and rescanning.
Subjective (75%): design quality review โ naming, error handling, abstractions, clarity. Starts at 0% until reviewed. The scan will prompt you when a review is needed.
Strict score is the north star: wontfix items count as open. The gap between overall and strict is your wontfix debt.
Import first, fix after โ import creates tracked state entries for correlation.
Target-matching scores trigger auto-reset to prevent gaming. Use the blind-review workflow described in your agent overlay doc (e.g. docs/CLAUDE.md, docs/HERMES.md).
Even moderate scores (60-80) dramatically improve overall health.
Stale dimensions auto-surface in next โ just follow the queue.
Integrity rules: Score from evidence only โ no prior chat context, score history, or target-threshold anchoring. When evidence is mixed, score lower and explain uncertainty. Assess every requested dimension; never drop one.
Review output format
Return machine-readable JSON for review imports. For --external-submit, include session from the generated template:
findings MUST match query.system_prompt exactly (including related_files, evidence, and suggestion). Use "findings": [] when no defects found. Import is fail-closed: invalid findings abort unless --allow-partial is passed. Assessment scores are auto-applied from trusted internal or cloud session imports. Legacy --attested-external remains supported.
Import paths
Robust session flow (recommended): desloppify review --external-start --external-runner claude โ use generated prompt/template โ run printed --external-submit command.
Durable scored import (legacy): desloppify review --import findings.json --attested-external --attest "I validated this review was completed without awareness of overall score and is unbiased."
Runners that support agent definitions (Cursor, Copilot, Gemini) can create a dedicated reviewer agent. Use this system prompt:
You are a code quality reviewer. You will be given a codebase path, a set of
dimensions to score, and what each dimension means. Read the code, score each
dimension 0-100 from evidence only, and return JSON in the required format.
Do not anchor to target thresholds. When evidence is mixed, score lower and
explain uncertainty.
See your editor's overlay section below for the agent config format.
Plan commands
desloppify plan reorder <cluster> top # move all cluster members at once
desloppify plan reorder <a> <b> top # mix clusters + findings in one reorder
desloppify plan reorder <pat> before -t X # position relative to another item/cluster
desloppify plan cluster reorder a,b top # reorder multiple clusters as one block
desloppify plan resolve <pat> # mark complete
desloppify plan reopen <pat> # reopen
desloppify backlog # broader non-execution backlog
Commit tracking
desloppify plan commit-log # see uncommitted + committed status
desloppify plan commit-log record # record HEAD commit, update PR description
desloppify plan commit-log record --note "why"# with rationale
desloppify plan commit-log record --only "smells::*"# record specific findings only
desloppify plan commit-log history# show commit records
desloppify plan commit-log pr# preview PR body markdown
desloppify config set commit_tracking_enabled false# disable guidance
After resolving findings as fixed, the tool shows uncommitted work, committed history, and a suggested commit message. After committing externally, run record to move findings from uncommitted to committed and auto-update the linked PR description.
Quick reference
desloppify next --count 5 # top 5 execution items
desloppify next --cluster <name> # drill into a cluster
desloppify backlog --count 5 # top 5 backlog items outside execution
desloppify show <pattern> # filter by file/detector/ID
desloppify show --status open # all open findings
desloppify plan skip --permanent "<id>" --note "reason" --attest "..."# accept debt
desloppify exclude <path> # exclude a directory from scanning
desloppify config show # show all config including excludes
desloppify scan --path . --reset-subjective # reset subjective baseline to 0
4. Fix Tool Issues Upstream
When desloppify itself appears wrong or inconsistent โ a bug, a bad detection, a crash, confusing output โ fix it and open a PR. If you can't confidently fix it, file an issue instead.
Fix and PR (preferred)
Clone the tool repo to a temp directory, make the fix there, and verify it works against the project you're scanning before pushing.
git clone https://github.com/peteromallet/desloppify.git /tmp/desloppify-fix
cd /tmp/desloppify-fix
git checkout -b fix/<short-description>
Make your changes, then run the test suite and verify the fix against the original project:
python -m pytest desloppify/tests/ -q
python -m desloppify scan --path <project-root> # the project you were scanning
Once it looks good, push and open a PR:
git add <files> && git commit -m "fix: <what and why>"
git push -u origin fix/<short-description>
gh pr create --title "fix: <short description>" --body "$(cat <<'EOF'
## Problem
<what went wrong โ include the command and output>
## Fix
<what you changed and why>
EOF
)"
Clean up after: rm -rf /tmp/desloppify-fix
File an issue (fallback)
If the fix is unclear or the change needs discussion, open an issue at https://github.com/peteromallet/desloppify/issues with a minimal repro: command, path, expected output, actual output.
