Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/09-meleantonio-awesome-econ-ai-stuff/_skills/engineering/code-simplifier

code-simplifier

Verified

Simplify and clean up code after changes are complete. Reduces complexity, improves readability, and ensures consistency.

Code Simplifier

Clean up and simplify code after making changes.

When to Use

Run this skill after completing a feature or fix to ensure the code is clean, readable, and maintainable.

Simplification Goals

Reduce Complexity

  • Break long functions into smaller, focused ones
  • Reduce nesting depth (max 3 levels)
  • Simplify complex conditionals
  • Extract magic numbers to named constants

Improve Readability

  • Use descriptive variable and function names
  • Add clarifying comments for non-obvious logic
  • Ensure consistent formatting
  • Remove unnecessary comments

Apply Pythonic Patterns

  • Use list/dict/set comprehensions where appropriate
  • Use with statements for resource management
  • Use enumerate() instead of manual indexing
  • Use zip() for parallel iteration
  • Use f-strings for formatting
  • Use pathlib for file paths

Clean Up

  • Remove unused imports
  • Remove unused variables
  • Remove commented-out code
  • Remove redundant code paths
  • Consolidate duplicate logic

Workflow

  1. Identify Changed Files

    • Focus on files modified in the current session
    • Or specify files/directories as arguments
  2. Analyze Each File

    • Check for simplification opportunities
    • Prioritize high-impact improvements
  3. Apply Simplifications

    • Make incremental changes
    • Preserve original behavior
    • Run tests after each change
  4. Format and Lint

    • Run ruff format .
    • Run ruff check --fix .
  5. Verify

    • Run tests: pytest
    • Ensure behavior unchanged

Arguments

Optionally specify files or directories to simplify.

Usage:

  • /code-simplifier - Simplify recently changed files
  • /code-simplifier src/module.py - Simplify specific file
  • /code-simplifier src/ - Simplify entire directory

Example Transformations

Before:

result = []
for i in range(len(items)):
    if items[i].is_valid == True:
        result.append(items[i].value)

After:

result = [item.value for item in items if item.is_valid]

Before:

if x != None:
    if y != None:
        if z != None:
            process(x, y, z)

After:

if all(v is not None for v in (x, y, z)):
    process(x, y, z)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall