Agent skill
unslopify
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/unslopify-shanev-skills
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?