gitignore
Skill2 starsChanged 4 months agoMITView on GitHub
Generate or tighten a .gitignore for the project's stack, and flag already-tracked files that should be ignored. Use when the user says "create a gitignore", "update my gitignore", "what should I ignore", "stop tracking this file", or "add X to gitignore".
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
- POSTTTT/SKILLstheir own version, first seen Jun 9, 2026
- jcsaaddupuy/badrobotstheir own version, first seen Feb 26, 2026
- sangre72/claude-skillstheir own version, first seen Jan 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- KhaledSaeed18/dotclaude★ 5same name
- jcsaaddupuy/badrobots★ 1same name
- POSTTTT/SKILLs★ 1same name
- sangre72/claude-skills★ 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.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Merge, don't clobber: If a .gitignore exists, add only the missing entries and keep the user's existing ones and grouping.
- Very specific: line 30
Don't ignore lockfiles (package-lock.json, poetry.lock, Cargo.lock) for applications — they should be committed.
- Very specific: line 31
Keep entries specific — avoid overly broad globs (*.json) that would hide real source/config.
- Very specific: line 32
Don't add committed, project-shared editor config to the ignore list (e.g.
- Distinctive: line 33
After writing, summarize what you added and list any untrack commands the user still needs to run.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Stack + current state
!ls package.json pyproject.toml requirements.txt Cargo.toml go.mod pom.xml build.gradle Gemfile composer.json 2>/dev/null
!cat .gitignore 2>/dev/null | head -60 || echo "No .gitignore yet"
!git ls-files 2>/dev/null | grep -iE '\.env$|\.log$|node_modules/|/dist/|/build/|\.DS_Store|__pycache__|\.pyc$|/target/|coverage/' | head -20 | sed 's/^/TRACKED-BUT-SHOULD-IGNORE: /'
Instructions
Generate or improve the .gitignore for this project (add anything from $ARGUMENTS too).
Method
- Detect the stack(s) from the manifests above — language, package manager, framework, and build tooling. A repo can need several sections (e.g. Node + Python).
- Cover the standard categories for each detected stack: dependency dirs (
node_modules/,vendor/), build output (dist/,build/,target/), caches (__pycache__/,.pytest_cache/,.gradle/), logs, coverage reports, env/secret files (.env,.env.local), editor/OS cruft (.DS_Store,.idea/,.vscode/— only if not project-shared), and lockfile/temp artifacts. - Merge, don't clobber. If a
.gitignoreexists, add only the missing entries and keep the user's existing ones and grouping. Group new entries under clear comment headers. - Flag already-tracked files. For any path in the
TRACKED-BUT-SHOULD-IGNORElist above, adding it to.gitignoreis not enough — git keeps tracking it. Tell the user and give the exact untrack command:git rm --cached <path>(or-rfor a directory), noting it stays on disk.
Rules
- Don't ignore lockfiles (
package-lock.json,poetry.lock,Cargo.lock) for applications — they should be committed. Do ignore them only for libraries if that's the project's convention; ask if unsure. - Keep entries specific — avoid overly broad globs (
*.json) that would hide real source/config. - Don't add committed, project-shared editor config to the ignore list (e.g. a checked-in
.vscode/settings.json). - After writing, summarize what you added and list any untrack commands the user still needs to run.
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.

