fec-refactoring

Installation
SKILL.md

Skill: Behavior-Preserving Refactoring

Purpose

Restructure live frontend code in small, evidence-backed steps while preserving the behavior users, callers, tests, routes, and integrations can observe.

Core Contract

Every execution follows these rules:

  1. Behavior Preservation — pure refactoring intentionally changes structure, not observable behavior.
  2. Green Baseline First — record available verification before editing.
  3. One Refactoring at a Time — one primary structural intent per step.
  4. Verify Every Step — run the narrowest meaningful check immediately after each step.
  5. Revert Before Repairing — if a new regression appears, revert that step before widening the edit.
  6. Separate Refactoring from Feature Work — behavior changes belong in a different workflow.
  7. Smallest Safe Refactoring First — prefer the narrowest transformation that fits the evidence.
  8. Stay Within the Diff Budget — stop when actual scope materially exceeds the planned scope.
Installs
2
GitHub Stars
23
First Seen
Sep 10, 2026