unbloat

Unbloat Command

Execute safe bloat remediation workflows with user approval at each step.

When To Use

Use this command when you need to:

• After bloat-scan identifies remediation targets
• Preparing for release
• Reducing codebase complexity

When NOT To Use

• Quick fixes that don't need structured workflow
• Already know the specific issue - fix it directly

Philosophy

• Safety First: Every change requires explicit approval (no auto-changes without review)
• Progressive: Start with high-confidence, low-risk changes first
• Reversible: Creates backup branches with clear rollback instructions

Usage

# Integrated workflow: scan + remediate
/unbloat

# Use existing bloat-scan report
/unbloat --from-scan bloat-report.md

# Auto-approve low-risk changes (still shows preview)
/unbloat --auto-approve low

# Preview changes without executing
/unbloat --dry-run

# Focus on specific area
/unbloat --focus code

Options

Option	Description	Default
--from-scan <file>	Use existing bloat-scan report	Run new scan
--auto-approve <level>	Auto-approve: low, medium, none	none
--dry-run	Preview all changes without executing	false
--focus <area>	Focus: code, docs, deps, or all	all
--backup-branch <name>	Custom backup branch name	backup/unbloat-{date}
--no-backup	Skip backup branch creation	false

Workflow Overview

1. Scan/Load: Run integrated Tier 1 scan or load from --from-scan report
2. Prioritize: Group by type (DELETE, REFACTOR, CONSOLIDATE, ARCHIVE) and risk
3. Backup: Create timestamped backup branch
4. Remediate: Interactive approval for each finding with preview
5. Verify: Run tests after each change, rollback on failure
6. Summary: Report actions, token savings, rollback instructions

For remediation type definitions and risk assessment, see: @module:remediation-types

Interactive Prompts