paulund/dev-simplify
dev-simplify/SKILL.md
Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/dev-simplify", "simplify this", "clean up".
$ install --global
skillsauthnpx skillsauth add paulund/skills dev-simplifyInstall 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 5, 2026, 6:41 AM106.0s1 file scanned
SKILL.md
- name:
- dev-simplify
- description:
- Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/dev-simplify", "simplify this", "clean up".
- category:
- dev
Core Workflow
- Identify complexity — redundant abstractions, dead code, over-engineered solutions
- Measure impact — does the complexity add value or just indirection?
- Propose simplifications — concrete refactors with before/after
- Verify behavior preservation — ensure functionality stays the same
- Apply changes — refactor, remove, consolidate
Simplification Targets
- [ ] Unused imports, variables, or functions
- [ ] Redundant abstractions (wrapper around a wrapper)
- [ ] Over-engineered patterns (factory for a single class)
- [ ] Deep nesting that can be flattened
- [ ] Duplicate logic that can be extracted
- [ ] Unnecessary indirection (interface with one implementation)
- [ ] Comments that explain what the code does (not why)
- [ ] Magic numbers or strings without constants
Output Format
- Complexity found — location and description
- Proposed simplification — specific code changes
- Risk assessment — what could break and how to test
- Application — execute the refactor or create an issue
Related Skills
paulund/quality-gate
development
VerifiedTrustedCommunity
Use when the user wants to run the project's lint + types + build sequence as a gate before pushing, opening a PR, or merging. Invoked by chained dev skills between phases. Trigger phrases - "/quality-gate", "run the quality gate", "check it builds".
2SKILL.mdUpdated May 10, 2026
paulund/pr-verify
tools
VerifiedTrustedCommunity
Use when the user wants to verify a PR's feature works at runtime by booting the dev server, exercising the affected UI via Chrome DevTools MCP, and posting a screenshot summary back to the PR. Idempotent — skips if `verified` or `verify-failed` is already on the PR. Trigger phrases - "/pr-verify", "verify this PR", "runtime check the pr".
2SKILL.mdUpdated May 10, 2026
paulund/pr-security-review
testing
VerifiedTrustedCommunity
Use when the user wants a security-focused review pass on a PR with findings actioned as commits on the same branch. Trigger phrases - "/pr-security-review", "security review and fix".
2SKILL.mdUpdated May 10, 2026
paulund/pr-open
testing
VerifiedTrustedCommunity
Use when the user wants to open a pull request for an already-pushed branch that implements a specific issue. Idempotent — returns the existing PR if one is already open for the branch. Trigger phrases - "/pr-open", "open the pr", "create pr for this branch".
2SKILL.mdUpdated May 10, 2026