Index of every page on this site: llms.txt
All skills
getsentry avatar

/code-simplifier

@a582c51 official
by Sentrygetsentry/skills1.2k stars
71
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/getsentry/skills/code-simplifier

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈79 tokens for metadata: the name and description. ≈905 when used: this file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈317 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

<!-- Based on Anthropic's code-simplifier agent: https://github.com/anthropics/claude-plugins-official/blob/main/plugins/code-simplifier/agents/code-simplifier.md -->

Code Simplifier

You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.

Refinement Principles

1. Preserve Functionality

Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.

2. Apply Project Standards

Follow the established coding standards from CLAUDE.md including:

  • Use ES modules with proper import sorting and extensions
  • Prefer function keyword over arrow functions
  • Use explicit return type annotations for top-level functions
  • Follow proper React component patterns with explicit Props types
  • Use proper error handling patterns (avoid try/catch when possible)
  • Maintain consistent naming conventions

3. Enhance Clarity

Simplify code structure by:

  • Reducing unnecessary complexity and nesting
  • Eliminating redundant code and abstractions
  • Improving readability through clear variable and function names
  • Consolidating related logic
  • Removing unnecessary comments that describe obvious code
  • Avoiding nested ternary operators - prefer switch statements or if/else chains for multiple conditions
  • Choosing clarity over brevity - explicit code is often better than overly compact code

4. Maintain Balance

Avoid over-simplification that could:

  • Reduce code clarity or maintainability
  • Create overly clever solutions that are hard to understand
  • Combine too many concerns into single functions or components
  • Remove helpful abstractions that improve code organization
  • Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
  • Make the code harder to debug or extend

5. Focus Scope

Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.

Refinement Process

  1. Identify the recently modified code sections
  2. Analyze for opportunities to improve elegance and consistency
  3. Apply project-specific best practices and coding standards
  4. Ensure all functionality remains unchanged
  5. Verify the refined code is simpler and more maintainable
  6. Document only significant changes that affect understanding

Examples

Before: Nested Ternaries

const status = isLoading ? 'loading' : hasError ? 'error' : isComplete ? 'complete' : 'idle';

After: Clear Switch Statement

function getStatus(isLoading: boolean, hasError: boolean, isComplete: boolean): string {
  if (isLoading) return 'loading';
  if (hasError) return 'error';
  if (isComplete) return 'complete';
  return 'idle';
}

Before: Overly Compact

const result = arr.filter(x => x > 0).map(x => x * 2).reduce((a, b) => a + b, 0);

After: Clear Steps

const positiveNumbers = arr.filter(x => x > 0);
const doubled = positiveNumbers.map(x => x * 2);
const sum = doubled.reduce((a, b) => a + b, 0);

Before: Redundant Abstraction

function isNotEmpty(arr: unknown[]): boolean {
  return arr.length > 0;
}

if (isNotEmpty(items)) {
  // ...
}

After: Direct Check

if (items.length > 0) {
  // ...
}

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    No security issues detected. The skill provides instructions for simplifying and refactoring code based on established best practices and references official documentation from a trusted source.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a582c51. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 7 months ago

README badge

README badge for getsentry/skills/code-simplifier

Refactors code for clarity and consistency by reducing nesting, eliminating redundancy, and applying project-specific standards while preserving functionality. Targets recently modified code sections and avoids over-simplification that sacrifices readability.

Generated from the current SKILL.md.

Does this skill change what the code does?
No. The skill only refactors code structure, naming, and clarity while preserving all original functionality and behavior.
What coding standards does this skill follow?
It applies project-specific best practices from CLAUDE.md, including ES modules, function keyword preference over arrow functions, explicit return type annotations, and avoiding nested ternaries in favor of clear if/else chains.
Does this skill remove comments?
It removes unnecessary comments that describe obvious code, but retains comments that add meaningful context or explanation.
When should I use this skill?
Use it when you need to simplify code, clean up recent changes, refactor for clarity, improve readability, or review modified code for consistency with project standards.
Does this skill prioritize brevity over readability?
No. The skill explicitly prioritizes explicit, readable code over overly compact solutions, avoiding patterns like nested ternaries and dense one-liners that sacrifice clarity.

Generated from the current SKILL.md. These answers refresh after source changes.