Skip to content
TrustedSkillsbeta
Back to all skills

Refactor Project

Checked
fradser·vlatest·backend·MIT

Automates backend code refactoring, improving readability, maintainability, and performance based on fradser's best practices.

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 fradser/dotclaude --skill refactor-project -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

fradser

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 fradser/dotclaude at 9815c4f485.

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

Commit
9815c4f485
Manifest
refactor/skills/refactor-project/SKILL.md
Scanned
4 files, 875 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 refactor-project skill helps improve existing codebases by identifying and applying common refactoring patterns. It can restructure code to enhance readability, maintainability, and performance. This includes tasks like extracting methods, renaming variables, and simplifying complex conditional logic within a project.

When to use it

  • You have a legacy codebase that is difficult to understand or modify.
  • A specific function or module is overly complex and needs simplification.
  • You want to improve the overall code quality and reduce technical debt.
  • You're preparing a project for new developers joining the team.

Key capabilities

  • Extract Method
  • Rename Variable
  • Simplify Conditional Logic
  • Restructure Codebase

Example prompts

  • "Refactor the calculate_total function in order_processing.py to improve readability."
  • "Can you extract a method from this block of code: [paste code snippet]"
  • "Identify and simplify any complex conditional logic within the user_authentication.js file."

Tips & gotchas

The skill's effectiveness depends on clear instructions and well-defined scope. It is best used incrementally, focusing on smaller sections of a codebase at a time to ensure manageable changes and easier review.