unslopify
战术代码清理侧重于类型严格性、单一责任、快速失败模式和 DRY。检测草率代码、解决方法、无声故障、上帝类和重复。用于在提交之前或代码审查期间快速检查代码质量。
📖 中文导读:战术代码清理侧重于类型严格性、单一责任、快速失败模式和 DRY。检测草率代码、解决方法、无声故障、上帝类和重复。用于在提交之前或代码审查期间快速检查代码质量。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: unslopify description: Tactical code cleanup focusing on type strictness, single responsibility, fail-fast patterns, and DRY. Detects sloppy code, workarounds, silent failures, god classes, and duplication. Use for quick code quality checks before committing or during code review.
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