PromptsEdge
FreeGitHubCoding

Refactor Code Without Behavior Change

Your AI restructures code to improve design without changing behavior, keeping tests green throughout. It plans the refactor, removes duplication or dead code, and manages review and gated commit with behavior-neutral diffs.

affaan-m on GitHub

Curated by PromptsEdge from a public repo · MIT license. All credit goes to the author.

What is this skill?

Actor · action · target: orch · refine · code. Thin wrapper over the shared engine in orch-pipeline.

When to use

  • Same behavior, better structure: extract modules, remove duplication, kill
  • Distinguish from siblings: if behavior is meant to change at all, this is the

Operation settings

  • Default size floor: standard — restructures touch multiple files.
  • Phase mask: 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No new behavior tests are written — the existing suite is the safety net.
  • First move (phase 4): confirm the relevant tests exist and are green before touching code; if coverage is thin, add characterization tests first. Then restructure in small steps, re-running tests after each.

How It Works

  1. Run the orch-pipeline engine with the settings above.
  2. For dead-code / duplication sweeps, delegate to the refactor-cleaner agent (it runs knip / depcheck / ts-prune and removes safely).
  3. Stop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
  4. Commit as refactor: — the diff must be behavior-neutral.

Example

orch-refine-code: extract the NWS HTTP client out of poller.py
→ confirm tests green → plan extraction  [GATE 1: approve]
→ move in small steps, tests green throughout → code-review
→ commit refactor:  [GATE 2: confirm]