hygiene
Skill1 starsChanged 7 days agoMITView on GitHub
Use before creating files or folders in a project, when a tool or build step produces output, and before committing. Keeps the repository clean: no stray folders or scratch files, correct .gitignore entries, no build output or IDE files in version control. Use it even when the task is about something else and only touches files on the side.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- NeuralInverse/neuralinversetheir own version, first seen Oct 8, 2026
- OpenCortexIDE/cortexidetheir own version, first seen Oct 8, 2026
- gitpod-io/openvscode-servertheir own version, first seen Oct 8, 2026
- CommsConnectgmbh/claude-starter-kittheir own version, first seen Oct 8, 2026
- kartikkabadi/synara-betatheir own version, first seen Sep 9, 2026
- kartikkabadi/skillstheir own version, first seen Aug 10, 2026
Used with
Projects with it also use add-policy, auto-perf-optimize and 10 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.
OpenCortexIDESkilladd-policy
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
Also in 4 projects that use this
MicrosoftSkillauto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
Also in 4 projects that use this
- MicrosoftSkill
chat-customizations-editor
Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.
Also in 4 projects that use this
- +9 more from microsoft
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- gitpod-io/openvscode-server★ 6.2ksame name
- NeuralInverse/neuralinverse★ 221same name
- OpenCortexIDE/cortexide★ 175same name
- cpkt9762/opencode-vscode-ide★ 17same name
- xAmirHamza77/OmniCode★ 12same name
- kartikkabadi/skills★ 9same name
- kartikkabadi/synara-beta★ 6same name
- CommsConnectgmbh/claude-starter-kit★ 0same name
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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Leave the tree as you found it, plus the intended change.
- Very specific: line 13
When something you add produces output, gitignore its folder in the same change, with the narrowest anchored pattern (/build/, not build).
- Very specific: line 14
Leave other tools' folders (.idea/, .vscode/, .claude/) alone unless asked.
- Distinctive: line 15
Don't reformat or reorder files you aren't otherwise changing.
- Distinctive: line 16
Before committing, check git status for anything unintended, and stage by path.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Repository hygiene
- Leave the tree as you found it, plus the intended change. Temporary files go in the session scratchpad or
$TMPDIR; remove what you created when done. - Build output, caches, IDE folders, OS files (
.DS_Store) and local env files never go into version control. - When something you add produces output, gitignore its folder in the same change, with the narrowest anchored pattern (
/build/, notbuild). - Leave other tools' folders (
.idea/,.vscode/,.claude/) alone unless asked. - Don't reformat or reorder files you aren't otherwise changing.
- Before committing, check
git statusfor anything unintended, and stage by path.
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.