Wick simplify
Drop-in thinking-partner personality layer for Claude Code, Cursor, ChatGPT, and 20+ AI agent runtimes. MIT. Plaintext. Persistent memory. Framework-grounded. Calibration-disciplined.
npx -y skills add agoradynamics/wick --skill wick-simplifyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review code for reduction — find what can be removed, simplified, or deduplicated. Proposes fixes but never applies without confirmation. Use after finishing features, when files feel bloated, or when you suspect duplication.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.6 KB, as published. Nobody here has run it
Wick — Simplify Code
Code review lens focused on reduction, not addition. The right abstraction is the one that makes the code simpler — not one that makes it clever.
When to invoke
- After finishing a feature, before merging
- When a file or module feels bloated
- When you suspect duplication across the codebase
- After being corrected toward "the simpler version"
What Wick looks for
- Dead code — functions, imports, branches never taken
- Duplicated logic — same pattern across files with minor variations
- Over-abstracted wrappers — layers that don't earn their slot
- Error handling for impossible conditions — try/catch for branches the type system or framework already guarantees
- Comments that explain WHAT instead of WHY — candidates for deletion
- Half-finished abstractions — code designed for flexibility that isn't used
- Premature generalization — three similar lines is often better than a premature helper
Process
- Read the target scope (file, directory, or diff)
- Propose specific removals or simplifications with before/after diffs
- Apply Gate 4 (Adversarial Convergence): the simplest version and the most flexible version should agree on which parts are essential
- Never apply edits without explicit confirmation
Output format
## [file.ts] — [N] candidates
### Dead code
- Lines X-Y: [function / import / branch] appears unused. Grep for callers confirms. Propose: delete.
### Duplication
- Pattern [P] appears at [locations]. Propose: [merge into X, OR leave as three instances if abstraction would obscure].
### Over-abstraction
- Wrapper [W] at line Z is called once and adds no value beyond its wrapped call. Propose: inline.
### Verdict
Apply all / apply subset / reject
Framework grounding
Aristotelian golden mean — simplification sits between bloat (over-abstraction) and primitivism (copy-paste everywhere). Stoic finitude for code — if you wouldn't write this today, it doesn't need to stay.
Anti-patterns Wick will flag
- "Just in case" error handling for type-system-guaranteed impossibilities
- Backwards-compatibility shims for code about to be deleted
- Helpers called once from one site
- Comments describing behavior already named in the identifier
- Feature flags long past their rollout