ilamanov/deslop
skills/deslop/SKILL.md
Remove AI-generated code slop and clean up code style
development
Updated May 29, 2026
$ install --global
skillsauthnpx skillsauth add ilamanov/skills deslopInstall 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: May 29, 2026, 2:33 AM157.2s1 file scanned
SKILL.md
- name:
- deslop
- description:
- Remove AI-generated code slop and clean up code style
Remove AI code slop
Check the diff against main and remove AI-generated slop introduced in the branch.
Focus Areas
- Unnecessary comments - Extra comments that are unnecessary or inconsistent with local style
- Defensive overkill - Defensive checks or try/catch blocks that are abnormal for trusted code paths
- Type escape hatches - Casts to
anyused only to bypass type issues - Deep nesting - Deeply nested code that should be simplified with early returns
- Single-use variables - Variables used once immediately after declaration; inline the RHS instead
- Single-use type definitions - Separate type or interface definitions used in only one place (React props, function parameters, return types, etc.); inline the type directly where it's used
- Re-exports from another file - There should be exactly one export of a thing, in the file that defines it. Don't re-export something defined elsewhere — whether the file is a pure barrel/pass-through or does real work alongside the re-exports. Drop the re-export lines and point importers at the defining module.
- Style drift - Other patterns inconsistent with the file and surrounding codebase
Guardrails
- Keep behavior unchanged unless fixing a clear bug.
- Prefer minimal, focused edits over broad rewrites.
- Keep the final summary concise (1-3 sentences).
Related Skills
ilamanov/codebase-conventions
tools
VerifiedTrustedCommunity
Generally-applicable conventions for how code is written and arranged — tooling/package manager, import style, file & component naming, comments, and where files live (colocation vs. global folders). Use whenever creating, naming, moving, or importing a file, running project commands, or deciding where a new module belongs. Consult BEFORE writing the code so the conventions are baked in, not retrofitted. If a convention below matches the work, apply it — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 30, 2026
ilamanov/frontend-patterns
development
VerifiedTrustedCommunity
Generally-applicable frontend/UI best practices. Use whenever building, modifying, or reviewing UI — adding a form/button/dialog/modal, wiring keyboard shortcuts, creating any interactive surface that submits a form, or any time TSX/JSX is being written or edited. Consult BEFORE writing the code so the patterns are baked in, not retrofitted. If a scenario described in the skill body matches the work, apply the pattern — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 26, 2026
ilamanov/backend-patterns
tools
VerifiedTrustedCommunity
Generally-applicable backend/data best practices. Use whenever writing or modifying backend/data code — API routes, server actions, DB writes, background jobs, agent tools, import flows, webhooks, paste handlers, or anywhere data enters the system. Consult BEFORE writing the code so the patterns are baked in, not retrofitted. If a scenario described in the skill body matches the work, apply the pattern — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 26, 2026
ilamanov/skill-improver
development
VerifiedTrustedCommunity
Runs on a schedule to mine recent Codex and Claude Code conversations across configured projects, find moments where things went off plan (the user had to steer, correct, abort, or re-explain), and propose targeted improvements to the specific skills that were in use at the time. Opens one pull request per run against the skills repo, with each proposed edit annotated with the concrete steering moment that motivated it. Also analyzes its own runs (the `skills` repo is one of the configured projects) so it iteratively improves itself. Use this skill when the user asks to "analyze recent conversations", "find what went wrong", "improve skills based on past runs", or sets up a scheduled run of skill-improver. Make sure to use this skill whenever the user mentions recursive skill improvement, post-mortem analysis of agent conversations, or automating skill quality based on real usage.
SKILL.mdUpdated May 25, 2026