refactor
- Repo stars 5,319
- License NOASSERTION
- Author updated Live
- Author repo unkey
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @unkeyed · NOASSERTION
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: refactor
description: Structural refactoring pass on changed code. Use after implementing a feature to improve code st…
category: engineering
runtime: no special runtime
---
# refactor output preview
## PART A: Task fit
- Use case: Structural refactoring pass on changed code. Use after implementing a feature to improve code structure, reduce duplication, and clean up APIs without changing behavior..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Structural refactoring pass on changed code. Use after implementing a feature to improve code structure, reduce duplication, and clean up APIs without changing behavior.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: refactor
description: Structural refactoring pass on changed code. Use after implementing a feature to improve code st…
category: engineering
source: unkeyed/unkey
---
# refactor
## When to use
- Structural refactoring pass on changed code. Use after implementing a feature to improve code structure, reduce duplic…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "refactor" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Refactor pass
Review the diff against main and perform a structural refactoring pass on all changed code in this branch.
Focus on:
Extract and consolidate: Pull repeated logic into shared functions. Merge near-duplicate code paths. Collapse unnecessary wrapper layers.
Improve structure: Flatten deep nesting. Break oversized functions into focused units. Move code closer to where it's used. Colocate related logic.
Clean up APIs and interfaces: Remove unused parameters, exports, and return values. Simplify function signatures. Make types tighter and more precise.
Reduce indirection: Inline trivial helpers that obscure intent. Remove pass-through functions that add no value. Shorten unnecessary call chains.
Fix naming: Rename variables, functions, and types so they say what they mean. Align naming with surrounding code conventions.
Rules:
- Do not change behavior. Every input/output must remain identical.
- Stay within the branch diff. Only refactor code that was added or modified in this branch. Do not refactor unrelated code unless it is directly entangled.
- Respect project conventions. Follow patterns and standards from CLAUDE.md and the surrounding codebase.
- Don't over-abstract. Three similar lines are fine. Only extract when duplication is real and likely to grow.
- Commit-ready output. The code should compile and pass tests after your changes.
Process:
- Read the full branch diff (
git diff main...HEAD) - Identify structural issues in the changed code
- Apply refactors file by file
- Run the project's type check / lint if available
- Report a 1-5 sentence summary of what you changed
Decide Fit First
Design Intent
How To Use It
Boundaries And Review