exec-refactoring
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when a task involves restructuring code, reducing tech debt, or improving maintainability.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
When your task involves refactoring, your primary directive is: Preserve existing behavior.
- Distinctive: line 9
Follow this Red-Green-Refactor loop strategy:
- Distinctive: line 12
Baseline: Ensure you understand the current inputs, outputs, and side effects of the target code.
- Distinctive: line 14
Preserve APIs: Do not change the public API or function signatures unless that is the explicit goal of the refactoring task.
- Distinctive: line 17
Do not refactor code outside the immediate scope of the task just because it "looks messy."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Refactoring Execution Strategy
When your task involves refactoring, your primary directive is: Preserve existing behavior. Do not mix feature development with refactoring.
Follow this Red-Green-Refactor loop strategy:
- Identify the Code Smell: Is it duplicated code, a God object, poor naming, or high cyclomatic complexity?
- Baseline: Ensure you understand the current inputs, outputs, and side effects of the target code.
- Smallest Safe Change: Break the refactoring down into atomic steps (e.g., extract function first, then rename variables).
- Preserve APIs: Do not change the public API or function signatures unless that is the explicit goal of the refactoring task. If you must, list the downstream consumers that will need updating.
- Justify: Explain why this structural change improves maintainability or performance.
Do not refactor code outside the immediate scope of the task just because it "looks messy."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.