Refactor module

Skill tmj-90/gaffer/runner/skills/refactor-module

Use when a ticket asks to restructure code without changing what it does — extract a function, split a file, rename for clarity, reduce duplication — with behaviour preserved. Invoke for "refactor X", "clean up the Y module", or "extract Z" where no behaviour change is intended.From its SKILL.md

Install

npx -y skills add tmj-90/gaffer --skill refactor-module

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 397 tokens by cl100k_base, as published. Nobody here has run it

Refactor a module

A refactor changes structure, not behaviour. The contract: tests are green before you start and green after, with no scope creep into new features or fixes.

Steps

Establish the safety net. Run the suite first (run-tests) and confirm it's green. If the module under refactor is thinly tested, add characterization tests (the add-unit-test skill) that pin the current behaviour before you touch anything.
Read the lore. Call search_lore (Memory MCP) for the repo's module boundaries, layering, and naming conventions so the new structure fits the codebase.
Refactor in small, behaviour-preserving steps — extract, rename, move, dedupe — re-running tests after each step. Keep the public interface stable unless the ticket explicitly allows changing it; update call sites if you do.
Change no behaviour. No new features, no bug fixes, no dependency changes riding along. If you spot a real bug, note it for a separate ticket — don't fix it here.
Confirm green after. Run the full suite and lint (run-tests, run-lint) and confirm identical behaviour and no new failures.
Evidence: before/after passing summaries (proving behaviour preserved) and a diff_summary. Then use the record-evidence skill and submit for review.

Rules

Behaviour-preserving only: tests green before and after, same outcomes.
No scope creep — no features, fixes, or dependency bumps in a refactor ticket.
Keep the public interface stable unless the AC says otherwise.
If you uncover a bug, log it separately; don't fix it inside the refactor.
Run on a branch (the create-branch skill), never a protected branch.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.