flpbalada/fb-skills

refactoring

Plan and apply behavior-preserving code refactors.

First seen May 7, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill refactoring

Summary

  • Plan and apply behavior-preserving code refactors.
  • Use when restructuring target files, reducing complexity, improving maintainability, applying framework or language best practices, improving type models, or reorganizing code while preserving public behavior and contracts.
  • For quick cleanup of recent edits use code-simplifier; for review-only architecture candidates use architecture-review.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,724 B
  • docs SUMMARY.md 413 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Refactoring

Improve structure. Keep behavior same. Avoid breaking changes.

Goal

Improve code structure without changing behavior. Reduce complexity only where it pays off.

Inputs

  • Target files, components, modules, or changed code.
  • Desired outcome or pain point.
  • Constraints and behavior that must not change.

Rules

  • Preserve behavior.
  • Make incremental changes.
  • Follow project conventions.
  • Keep changes minimal.
  • Avoid over-refactoring.
  • Do not change public contracts without request.
  • Verify when checks exist.

Flow

  1. Analyze target code.
  2. Identify goal, constraints, patterns, and anti-patterns.
  3. Load relevant skills only when they materially improve the refactor.
  4. Define smallest safe steps.
  5. Apply changes incrementally.
  6. Verify behavior is unchanged.

Skill Hints

  • Naming issues: naming-cheatsheet.
  • Abstraction issues: code-architecture-wrong-abstraction.
  • React: react-use-state, react-useeffect-avoid, react-use-client-boundary.
  • TypeScript: typescript-best-practices, typescript-interface-vs-type, typescript-satisfies-operator.
  • Project layout: project-structure.

Output

## Refactor
- [changed area]

## Behavior
- [behavior preserved]

## Verification
- [check run or reason not run]