Best use case
refactor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Identify code smells and execute safe refactorings
Teams using refactor should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/refactor/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/refactor/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/refactor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How refactor Compares
| Feature / Agent | refactor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Identify code smells and execute safe refactorings
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Analyze and refactor the specified code. Target: $ARGUMENTS (file path, module, or area to refactor) Steps: 1. Read the target code and understand its purpose 2. Identify code smells (long functions, duplication, high complexity) 3. Propose specific refactorings with rationale 4. Implement refactorings one at a time, verifying tests pass after each 5. Report what was changed and why
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.