not-matthias/simplify
modules/home/programs/cli-agents/shared/skills/simplify/SKILL.md
Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after completing an implementation to catch redundancy, dead code, and over-engineering before committing.
$ install --global
skillsauthnpx skillsauth add not-matthias/dotfiles-nix 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: Apr 20, 2026, 6:02 AM14.5s1 file scanned
SKILL.md
- name:
- simplify
- description:
- Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after completing an implementation to catch redundancy, dead code, and over-engineering before committing.
Simplify
Review your implementation before stopping. Run through each check below and fix issues in-place.
Checklist
- Simpler approach? Is there a more straightforward way to achieve the same result? Fewer moving parts, less indirection, fewer abstractions.
- Redundant code? Are there duplicated blocks, near-identical functions, or copy-pasted logic that should be consolidated?
- Duplicate logic? Did you introduce something that already exists elsewhere in the codebase? Check for existing helpers, utilities, or patterns before adding new ones.
- Dead code? Are there unused imports, variables, functions, or commented-out blocks that should be removed?
- Over-engineering? Did you add abstractions, configurability, error handling, or future-proofing that isn't needed for the current task? Three similar lines of code is better than a premature abstraction. Do not remove helpful abstractions that improve organization and maintainability.
- Clarity over brevity? Prefer explicit, debuggable code over dense one-liners.
- Readable conditionals? Avoid nested ternaries when they hurt readability; use clearer conditionals.
- Tests still pass? If the project has tests, run them. If any fail due to your changes, fix them before finishing.
Rules
- Preserve functionality: never change behavior; only simplify structure and readability.
- Only review files that were changed in this session or are staged in git.
- Fix issues directly — don't just report them.
- Only flag high-confidence issues. False positives are worse than missed nits.
- If no issues are found, briefly confirm the implementation is clean (one sentence).
- Do NOT add comments, docstrings, or type annotations that weren't there before.
- Do NOT refactor surrounding code that wasn't part of the original change.
Related Skills
not-matthias/pi-agent
tools
VerifiedTrustedCommunity
Spawn the pi coding agent with a specific model/provider. Use when asked to run pi with a particular model, switch pi's model, use DeepSeek V4 Flash/Pro in pi, or look up pi's --model/--provider/--models CLI flags and thinking-level shorthand.
9SKILL.mdUpdated Jun 3, 2026
not-matthias/zoxide-nav
development
VerifiedTrustedCommunity
Navigate to directories using zoxide (frecency-based directory jumper). Use when the user says "go to", "navigate to", "cd to", "jump to" a project or directory by nickname/partial name (e.g. "go to my dotfiles", "jump to dot").
9SKILL.mdUpdated Apr 20, 2026
not-matthias/zellij
tools
VerifiedTrustedCommunity
Use when manipulating Zellij sessions, creating tabs or panes, sending commands to panes, capturing output, or looking up Zellij CLI commands for terminal multiplexer operations
9SKILL.mdUpdated Apr 20, 2026
not-matthias/writing-style
development
VerifiedTrustedCommunity
Emulates not-matthias's technical blog writing style. Use when writing blog posts, technical articles, README content, or any long-form technical prose. Produces investigation-driven, first-person narratives with dry humor, practical code examples, and concrete takeaways.
9SKILL.mdUpdated Apr 20, 2026