code-simplifier_skill

Overview

This skill simplifies and refines code for clarity, consistency, and maintainability while preserving exact functionality. It targets recently modified code and applies project-specific standards to produce readable, explicit code. I prioritize preserving behavior over shrinking lines and avoid clever shortcuts that harm maintainability.

How this skill works

I identify recently changed sections and analyze them for redundant logic, excessive nesting, or inconsistent naming. I then refactor using the project's coding standards (import ordering, explicit function declarations, consistent naming, clear error handling) and replace convoluted constructs with explicit alternatives. Changes are limited to touched code unless a broader review is requested, and I document only meaningful adjustments that affect comprehension.

When to use it

• After writing complex or dense code that could be clearer
• When asked to "simplify", "clean up", or "refactor" code
• When code has grown hard to follow or has inconsistent style
• Before merging a change to ensure it follows project standards
• When you want maintainable dotfiles or config code (Lua, Nix, shell)

Best practices

• Preserve exact behavior — do not change outputs or side effects
• Prefer explicit, readable code over terse one-liners or nested ternaries
• Follow project rules for imports, function declarations, and naming
• Consolidate related logic but avoid combining unrelated concerns
• Remove redundant abstractions and clarify intent with names and small helpers

Example use cases

• Refactor a recently added Lua module for Neovim to use clearer helper functions
• Simplify a complex shell/Nix configuration that mixes concerns and has deep nesting
• Clean up a JavaScript/TypeScript utility after a rapid prototyping pass to match ES module rules
• Reduce cognitive load in a tmux or fish config by removing duplication and clarifying names
• Make recent changes easier to test and extend without altering behavior