improve
Skill423 starsChanged 3 months agoMITView on GitHub
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions.
66 other projects use a version of this.
Adopted by
Most recently taken up by
- LeonardiFranco/skillstheir own version, first seen Nov 8, 2026
- droxey/skillstheir own version, first seen Nov 8, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- PunGrumpy/docker-doctortheir own version, first seen Nov 8, 2026
- crbnos/carbontheir own version, first seen Nov 7, 2026
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
Used with
Projects with it also use deploy-platform, setup-platform and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agno-agiSkilldeploy-platform
Deploy this AgentOS using its own provider instructions, configure JWT verification, and verify the public service. Use for first deployment, redeployment, or production configuration changes.
Also in 4 projects that use this
agno-agiSkillsetup-platform
Set up this AgentOS from a fresh clone — confirm Docker, configure .env, boot the containers, prove the MCP endpoint live, connect the AgentOS UI, then build the user's first agent. Use when the user asks to set up the platform, get started, or bring this repo up on a new machine.
Also in 4 projects that use this
MicrosoftSkillcreate-agent
Create a new MCS2 Copilot Studio agent and PAC-connected local workspace with `pac copilot init`, then optionally add modern instructions, skills, tools, knowledge, and settings before synchronizing it. Use when the user asks to create, scaffold, initialize, or build a Copilot Studio agent.
Also in 5 projects that use this
HeshamFSSkillloop
Run a command or check on a recurring interval
Also in 5 projects that use this
admin-remixSkillworkspace
Google Workspace administration - manage users, groups, email, Drive, calendars, and devices through natural conversation. Triggers on: Google Workspace, G Suite, user management, group management, admin tasks, offboarding, onboarding, email forwarding, Drive permissions, suspended users, organizational units, ChromeOS devices, audit logs, admin reports.
Also in 3 projects that use this
AmirofcodesSkillgoal
Use when the user starts, manages, or asks about an OpenClaw goal mode with /goal. Enforces a bounded goal contract, visible progress blocks, proof requirements, stop conditions, and honest limitation language when no runtime goal-loop plugin is active.
Also in 4 projects that use this
- +3 more from agno-agi
Other versions66 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 66
- motiondivision/motion★ 35ksame name
- shadcn/improve★ 9.2ksame name
- legions-developer/evilcharts★ 3.2ksame name
- crbnos/carbon★ 2.8ksame name
- openstatusHQ/data-table-filters★ 2.3ksame name
- kimdre/doco-cd★ 1.8ksame name
- SethGammon/Citadel★ 927same name
- gadicc/yahoo-finance2★ 815same name
- shobcoder/shob★ 575same name
- AkaraChen/aghub★ 271same name
56 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- architectureSkill
- codex-issue-coordinatorSkill
- html-docSkill
- planSkill
- requirementsSkill
- reviewSkill
- specSkill
- task-to-prSkill
- testSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
5
Distinctive
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 16
Read the target, its tests, and relevant surrounding code.
- Distinctive: line 17
If that behavior lacks tests, add focused coverage and run it against the unchanged code.
- Distinctive: line 21
Run tests and checks that cover behavior the refactor can affect.
- Distinctive: line 29
Do not add product scope or absorb unrelated cleanup.
- Distinctive: line 30
Prefer a few clear edits over a broad rewrite.
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Improve
Make code easier to understand without changing what it does. Reduce the layers a reader must trace and the hidden state they must remember.
Process
- Identify the target from the request, current diff, or recently changed code.
- Read the target, its tests, and relevant surrounding code. State the behavior that must not change.
- If that behavior lacks tests, add focused coverage and run it against the unchanged code. Commit the passing test-only change before refactoring. If automated tests cannot exercise the behavior, explain why and give other evidence.
- Find unnecessary complexity, duplication, dead code, weak names, awkward boundaries, and abstractions that cost more than they help.
- Make focused improvements by deleting, deduplicating, renaming, simplifying, extracting, or inlining.
- Preserve public interfaces, data shapes, errors, and user-visible behavior unless the user explicitly asks to change them.
- Run tests and checks that cover behavior the refactor can affect. Report what improved, what behavior was preserved, and the evidence.
Return
State what became simpler, what behavior stayed the same, and which checks prove it. Name any behavior that remains unverified.
Boundaries
- Do not add product scope or absorb unrelated cleanup.
- Prefer a few clear edits over a broad rewrite.
- Preserve behavior even when a redesign would be easier.
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.

