Stats
Actions
Tags
From refactor
Apply Change Function Declaration when you see Mysterious Name, Long Parameter List, Alternative Classes with Different Interfaces. Function names match what they actually do; parameter lists carry only what the function needs, in the order callers expect.
How this skill is triggered — by the user, by Claude, or both
Slash command
/refactor:change-function-declarationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Target state:** Function names match what they actually do; parameter lists carry only what the function needs, in the order callers expect.
Target state: Function names match what they actually do; parameter lists carry only what the function needs, in the order callers expect.
Why apply it: Call sites read fluently; mismatches between expectation and behavior surface immediately at the boundary.
Pitfall: Mass renames or signature shifts ripple to every caller; refactor in tooling-supported steps and update tests with each batch.
// Avoid:
function circum(radius) {
return 2 * Math.PI * radius;
}
// Prefer:
function circumference(radius) {
return 2 * Math.PI * radius;
}
Removes smells: Mysterious Name, Long Parameter List, Alternative Classes with Different Interfaces
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub wallacedrew/ritl --plugin refactor