Loading...
Loading...
Found 65 Skills
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.
Use when refactoring code for clarity without changing behavior, when working code is harder to read, maintain, or extend than it should be, or when reviewing accumulated complexity.
Simplifies working code and project-memory documentation through evidence-backed, root-cause changes. Use when code has dead, duplicated, speculative, or overbuilt surface area, or when docs/project-memory needs concise, canonical, affirmative wording without changing unverified architecture facts.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
deslop a diff, remove AI slop and over-engineering while preserving exact behavior. Triggers: /deslop, remove AI slop, clean AI artifacts, strip over-engineered patterns, simplify code, review changes for bloat. Flags: --staged, --unstaged, --base <branch>.
Run code-simplifier on current branch/PR changes to show a cleaned-up version
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
Finish the current work Boris-style. Test it end-to-end, simplify the diff, then open a PR and stop. The PR's CI gate and the reviewer own everything after that. Use when the user says "/go", "go", or ends a request with "then go".