Unslopify
Tactical code cleanup focused on immediate quality issues.
Usage
/unslopify # Run all 4 analyzers in parallel
/unslopify --types # Type strictness only
/unslopify --srp # Single responsibility only
/unslopify --fail-fast # Fail-fast only
/unslopify --dry # DRY only
Analyzers
| Analyzer | Question |
|---|---|
| type-strictness-analyzer | Are types as strong as possible? |
| srp-analyzer | Does each unit have one job? |
| fail-fast-analyzer | Do errors surface immediately? |
| dry-analyzer | Is there duplicated code? |
What's "Sloppy"?
| Sloppy | Clean |
|---|---|
any, interface{}, unwrap() |
Strong domain types |
| God classes, 500-line functions | Focused, single-purpose |
catch (e) { } swallowed |
Explicit error handling |
// HACK: comments |
Fix the root cause |
| Silent fallbacks | Fail fast, fail loud |
| Copy-pasted code blocks | Extracted helpers/utilities |
When to Use
- Quick code review
- Before committing
- Cleaning up tech debt
- Checking for obvious issues
Supported Languages
- TypeScript / JavaScript
- Go
- Rust
Reference Documentation
- Type Strictness
- Single Responsibility
Converted and distributed by TomeVault — claim your Tome and manage your conversions.