Skip to content
TrustedSkillsbeta
Back to all skills

Refactoring Surgeon

Checked
erichowens·vlatest·backend·MIT

Safely restructures complex backend code into cleaner, more maintainable modules while preserving functionality.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add curiositech/some_claude_skills --skill refactoring-surgeon -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

erichowens

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned erichowens/some_claude_skills at 6713fc7a64.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6713fc7a64
Manifest
.claude/skills/refactoring-surgeon/SKILL.md
Scanned
8 files, 1,675 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Refactoring Surgeon skill assists AI agents in safely restructuring complex backend code to improve its quality and maintainability without altering its behavior. It focuses on applying established refactoring techniques to address specific code smells and patterns, ensuring functionality remains consistent throughout the process. This skill is particularly useful for improving existing codebases rather than creating new ones.

When to use it

  • When dealing with "bloaters" like long methods or large classes that hinder understanding and modification.
  • To simplify complex conditional logic (e.g., switch statements) into more manageable polymorphic structures.
  • For gradually migrating legacy codebases using patterns like the Strangler Fig approach.
  • When a codebase needs organization, such as replacing magic numbers with named constants or introducing parameter objects to reduce long parameter lists.
  • To address "change preventers" where changes in one area require modifications across multiple classes.

Key capabilities

  • Extraction: Extract Method, Extract Class, Extract Interface
  • Movement: Move Method, Move Field, Inline Method
  • Simplification: Replace Conditional with Polymorphism, Decompose Conditional
  • Organization: Introduce Parameter Object, Replace Magic Numbers
  • Legacy Migration: Strangler Fig, Branch by Abstraction, Parallel Change
  • Provides a reference guide to common code smells and associated refactoring techniques.

Example prompts

  • "Refactor this method using the Extract Method technique."
  • "Apply the Strangler Fig pattern to migrate this legacy module."
  • "Replace this switch statement with polymorphism."
  • "Introduce a parameter object for this function that has five parameters."

Tips & gotchas

  • Tests are essential: Refactoring should always be accompanied by existing tests to ensure behavior is preserved. Write characterization tests first if coverage is lacking.
  • Small, incremental changes: Avoid "Big Bang Refactoring" - make small, frequent commits and test after each change.
  • Focus on refactoring, not feature addition: The goal is to improve the structure of existing code, not add new functionality.