Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Refactor Planner

Checked
patricio0312rev·vlatest·frontend·MIT

Helps with frontend development, refactoring as part of productivity and workflow automation workflows.

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 patricio0312rev/skills --skill frontend-refactor-planner -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
frontend/frontend-refactor-planner/SKILL.md
Scanned
1 file, 38 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

The frontend-refactor-planner skill analyzes existing codebases to generate structured strategies for modernizing legacy applications without breaking functionality. It identifies technical debt, suggests architectural improvements, and outlines step-by-step migration paths tailored to specific frameworks.

When to use it

  • Planning a major version upgrade (e.g., React 16 to React 18) while minimizing downtime.
  • Refactoring monolithic applications into micro-frontends or modular components.
  • Identifying security vulnerabilities and performance bottlenecks in outdated libraries.
  • Creating a roadmap for migrating from jQuery or AngularJS to modern standards.

Key capabilities

  • Scans current code structure to detect deprecated patterns and anti-patterns.
  • Generates prioritized lists of refactoring tasks based on impact and risk.
  • Proposes specific tooling and libraries suitable for the target environment.
  • Outputs actionable implementation plans including testing strategies.

Example prompts

  • "Analyze my current React codebase and create a plan to migrate to Next.js 14 with minimal feature disruption."
  • "Identify all instances of jQuery in this project and suggest a step-by-step refactor to vanilla JavaScript or Alpine.js."
  • "Generate a refactoring roadmap for our AngularJS application, focusing on separating business logic from the view layer."

Tips & gotchas

Ensure you provide access to your repository or paste relevant code snippets, as the planner relies on analyzing actual implementation details. While it offers strategic guidance, always review its suggestions against your team's specific constraints before executing changes in production.