Skip to content
TrustedSkillsbeta
Back to all skills

Refactoring Expert

Checked
votruongdanh·vlatest·backend

Refactors complex backend codebases, improving readability, maintainability, and performance based on best practices.

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 votruongdanh/sentiment --skill refactoring-expert -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

votruongdanh

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 votruongdanh/sentiment at a417a6a2b1.

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

Scanned
1 file, 370 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

This skill, refactoring-expert, helps improve existing codebases. It can analyze code and suggest improvements to make it more readable, maintainable, and efficient. The agent will identify areas of technical debt and propose concrete steps for refactoring.

When to use it

  • Legacy Code: When working with older code that is difficult to understand or modify.
  • Code Review: To assist in code reviews by automatically identifying potential refactoring opportunities.
  • Performance Optimization: To pinpoint areas of inefficient code and suggest improvements for better performance.
  • Technical Debt Reduction: As part of a larger effort to systematically reduce technical debt within a project.

Key capabilities

  • Code analysis
  • Refactoring suggestions
  • Identification of technical debt
  • Improve readability
  • Enhance maintainability

Example prompts

  • "Analyze this Python function and suggest ways to refactor it for better readability."
  • "Identify any potential performance bottlenecks in this Java class."
  • "This code is difficult to understand. Can you suggest improvements?"

Tips & gotchas

The skill's effectiveness depends on the quality of the input code; poorly written or overly complex code may yield less precise suggestions. Providing context about the codebase and desired outcomes can improve results.