kitfunso/de-sloppify
skills/de-sloppify/SKILL.md
Two-pass development pattern for cleaner output. Use after implementing a large feature, complex refactor, or any substantial code change. Separates implementation from cleanup for better results. Two focused agents beat one constrained agent.
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add kitfunso/omniskill de-sloppifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 10:34 PM330.8s2 files scanned
SKILL.md
- name:
- de-sloppify
- description:
- Two-pass development pattern for cleaner output. Use after implementing a large feature, complex refactor, or any substantial code change. Separates implementation from cleanup for better results. Two focused agents beat one constrained agent.
De-Sloppify Pattern
Two focused passes beat one constrained pass. First implement, then clean up in a separate pass with fresh eyes.
The Problem
When you ask for implementation + quality in one pass, you get neither done well. The model tries to satisfy conflicting constraints: "write fast" vs "write clean."
The Pattern
Pass 1: Implement
Focus entirely on making it work. Get the feature done, tests passing, logic correct. Don't worry about:
- Console.log statements
- Commented-out code
- Verbose variable names
- Tests that test language behavior rather than business logic
- Overly defensive error handling
Pass 2: De-Sloppify
Fresh review of all changes. Check for and fix:
- Dead code — Remove commented-out code, unused imports, unreachable branches
- Debug artifacts — Remove console.log, print(), debugger statements
- Test quality — Remove tests that test the type system or framework behavior, not your code
- Over-engineering — Simplify abstractions that only have one implementation
- Naming — Rename vague variables (
data,result,temp,x) - Error handling — Remove catch blocks that just re-throw, add handling where it's actually needed
- Consistency — Match existing code style and patterns in the codebase
Usage
After implementing a feature:
"Review all the changes we just made. De-sloppify: remove dead code, debug artifacts,
tests of language behavior, and over-engineering. Run the test suite after cleanup."
When to Use
- After any implementation that touched 3+ files
- After a rapid prototyping session
- Before creating a PR
- After a long debugging session that left artifacts
Related Skills
kitfunso/retro
development
VerifiedTrustedCommunity
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint.
SKILL.mdUpdated Apr 23, 2026
kitfunso/qa
development
VerifiedTrustedCommunity
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
SKILL.mdUpdated Apr 23, 2026
kitfunso/qa-only
development
VerifiedTrustedCommunity
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.
SKILL.mdUpdated Apr 23, 2026
kitfunso/plan-eng-review
testing
VerifiedTrustedCommunity
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation.
SKILL.mdUpdated Apr 23, 2026