name	refactor
description	Safely refactor code with test coverage as a safety net
argument-hint	[target to refactor — file, function, or pattern]
disable-model-invocation	true

Refactor $ARGUMENTS safely.

Process

1. Understand the current state

Read the code and its tests
Identify what the code does, its callers, and its dependencies
If there are no tests, WRITE TESTS FIRST — you need a safety net before changing anything

2. Plan the refactoring

State what you're changing and why (clearer naming, reduced duplication, better structure)
List the specific transformations (extract function, inline variable, move module, etc.)
Check: does this change any external behavior? If yes, this isn't a refactor — reconsider.

3. Make changes in small, testable steps

One transformation at a time
Run tests after EACH step — not at the end
If a test breaks, undo the last step and make a smaller change

4. Verify

All existing tests pass
Lint and typecheck pass
The public API hasn't changed (unless that was the explicit goal)
The code is objectively simpler — fewer lines, fewer branches, clearer names

Rules

If you can't run the tests, don't refactor
Never mix refactoring with behavior changes in the same commit
If the refactoring is large (10+ files), break it into multiple commits

Más de este repositorio

mismo repositorio

debug-fix

zebbern/termstack

Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

2026-04-164

pr-review

zebbern/termstack

Review code changes or a pull request — delegates to specialist agents for code quality, security, performance, and documentation.

2026-04-164

ship

zebbern/termstack

Scan changes, commit, push, and create a PR — with confirmation at each step

2026-04-164

tdd

zebbern/termstack

Test-Driven Development loop — write a failing test first, then the minimum code to pass it, then refactor. Repeat.

2026-04-164

test-writer

zebbern/termstack

Write comprehensive tests for new or changed code. Use automatically when new features are added, functions are created, or behavior is modified.

2026-04-164

algorithmic-art

zebbern/termstack

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

2026-04-104

name	refactor
description	Safely refactor code with test coverage as a safety net
argument-hint	[target to refactor — file, function, or pattern]
disable-model-invocation	true

Refactor $ARGUMENTS safely.

Process

1. Understand the current state

Read the code and its tests
Identify what the code does, its callers, and its dependencies
If there are no tests, WRITE TESTS FIRST — you need a safety net before changing anything

2. Plan the refactoring

State what you're changing and why (clearer naming, reduced duplication, better structure)
List the specific transformations (extract function, inline variable, move module, etc.)
Check: does this change any external behavior? If yes, this isn't a refactor — reconsider.

3. Make changes in small, testable steps

One transformation at a time
Run tests after EACH step — not at the end
If a test breaks, undo the last step and make a smaller change

4. Verify

All existing tests pass
Lint and typecheck pass
The public API hasn't changed (unless that was the explicit goal)
The code is objectively simpler — fewer lines, fewer branches, clearer names

Rules

If you can't run the tests, don't refactor
Never mix refactoring with behavior changes in the same commit
If the refactoring is large (10+ files), break it into multiple commits