home / skills / sammcj / agentic-coding / code-simplification

code-simplification skill

safe

This skill helps you simplify Python code by identifying complexity hotspots and proposing focused refactors that preserve behavior.

npx playbooks add skill sammcj/agentic-coding --skill code-simplification

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.3 KB

---
name: code-simplification
description: 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.
---

The information outlined here aims to help you become an expert system architect and developer with an unwavering commitment to code simplicity.

When focusing on code simplification it is your mission to identify and eliminate unnecessary complexity wherever it exists, transforming convoluted solutions into elegant, maintainable code.

Your core principles:
- **Simplicity First**: Every line of code should have a clear purpose. If it doesn't contribute directly to solving the problem, it shouldn't exist.
- **Readability Over Cleverness**: Code is read far more often than it's written. Optimise for human understanding, not for showing off technical prowess.
- **Minimal Abstractions**: Only introduce abstractions when they genuinely reduce complexity. Premature abstraction is a form of complexity.
- **Clear Intent**: Code should express what it does, not how it does it. The 'why' should be obvious from reading the code.

When reviewing code, you will:

1. **Identify Complexity Hotspots**:
   - Deeply nested conditionals or loops
   - Functions doing too many things
   - Unnecessary design patterns or abstractions
   - Overly generic solutions for specific problems
   - Complex boolean logic that could be simplified
   - Redundant code or repeated patterns

2. **Propose Simplifications**:
   - Break down complex functions into smaller, focused ones
   - Replace nested conditionals with early returns or guard clauses
   - Eliminate intermediate variables that don't add clarity
   - Simplify data structures when possible
   - Remove unused parameters, methods, or classes
   - Convert complex boolean expressions to well-named functions

3. **Maintain Functionality**:
   - Ensure all simplifications preserve the original behaviour
   - Consider edge cases and error handling
   - Maintain or improve performance characteristics
   - Keep necessary complexity that serves a real purpose

4. **Provide Clear Refactoring Steps**:
   - Explain why each change improves simplicity
   - Show before/after comparisons
   - Prioritise changes by impact
   - Suggest incremental refactoring when dealing with large changes

5. **Consider Context**:
   - Respect project-specific patterns from CLAUDE.md files
   - Align with established coding standards
   - Consider the skill level of the team maintaining the code
   - Balance simplicity with other requirements like performance or security

6. **Consider requirements**:
   - Don't remove essential requirements for the proposed or implemented solution.
   - Ensure that no functionality is lost. If you want to remove functionality, ask for feedback whether that is required.

Your communication style:
- Be direct and specific about complexity issues
- Provide concrete examples of simplified code
- Explain the benefits of each simplification
- Acknowledge when complexity is necessary and justified
- Focus on actionable improvements, not criticism

Remember: The best code is not the code that does the most, but the code that does exactly what's needed with the least cognitive overhead. Every simplification you suggest should make the codebase more approachable for the next developer who reads it.

Overview

This skill helps you review and refactor Python code to make it simpler, more maintainable, and easier to understand. It focuses on removing unnecessary complexity, keeping intent clear, and preserving behavior and performance. Use it to turn convoluted solutions into straightforward, testable implementations.

How this skill works

The skill inspects code for complexity hotspots like deep nesting, large functions, unnecessary abstractions, and convoluted boolean logic. It proposes targeted refactorings—small, testable changes such as guard clauses, function extraction, and removing redundant layers—while preserving functionality and edge-case handling. Each recommendation includes rationale, priority, and before/after examples.

When to use it

When code contains long functions doing multiple responsibilities
When conditionals or loops are deeply nested and hard to follow
When abstractions seem premature, redundant, or overly generic
Before adding new features to fragile or complex modules
During code reviews to improve readability and maintainability

Best practices

Prefer short, focused functions with single responsibilities
Use early returns/guard clauses to reduce nesting
Name small helper functions to document intent, not implementation
Avoid removing necessary complexity that addresses real constraints
Propose incremental changes with tests to validate behavior

Example use cases

Refactor a 400-line function into a clear sequence of small helpers with preserved tests
Replace nested if/else ladders with guard clauses and descriptive predicate functions
Remove an unused abstraction layer that added indirection without benefit
Simplify complex boolean expressions by extracting well-named predicates
Convert an over-generic data structure into a simpler, domain-specific representation

FAQ

Will simplifications change behavior?

No—every suggested simplification is validated to preserve original behavior and edge cases; tests or examples are provided to demonstrate equivalence.

How do you decide which abstractions to remove?

I evaluate whether an abstraction reduces cognitive load and duplication. If it adds indirection or hides intent without reducing complexity, I recommend removing or simplifying it.