setup-gitignore
/setup-gitignore
Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
- Author
- OutlineDriven ↗
- Repository
- odin-codex-plugin ↗
- Licence
- Apache-2.0
- Last repository change
- 08.07.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.07.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/compose-gitignore.sh
What it does and when to use it
Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
Triggers from the description
Original author description
Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
How it works
- Scope
- Sources composed (in order)
- Workflow
- Idempotence contract
SKILL.md preview
--- name: setup-gitignore description: Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status. --- Initialize or idempotently revise the current repo's `.gitignore` — never the global excludesfile. ## Scope Per-repo only. Never read or write `~/.gitignore`, `~/.config/git/ignore`, or run `git config --global`. The user's global excludesfile handles cross-machine noise; this skill handles language/tool specifics for the current repo. ## Sources composed (in order) 1. **gitignore.io** — templates keyed by detected language/framework (requires network) 2. **AI tooling** — bundled patterns from `references/AI-TOOLING.md` 3. **IDE / editor** — bundled patterns from `references/IDE-EDITOR.md` 4. **Empirical** — untracked paths from `git status`, confirmed interactively ## Workflow ### 1. Detect repo root ```sh git rev-parse --show-toplevel ``` Abort with a clear error if not inside a git repo. ### 2. Detect languages Read `references/LANGUAGE-DETECTION.md` for the manifest → gitignore.io key table. Scan manifests: ```sh fd --max-depth 2 -t f ``` Match filenames against the detection table; build a comma-separated key list (e.g., `rust,node,typescript`). If no manifests detected, use an empty key list (bundled blocks still apply). ### 3. Snapshot existing .gitignore If `.gitignore` exists, snapshot it before any modification: ```sh cp .gitignore /tmp/gitignore-snapshot-$(date +%s).bak ``` ### 4. Surface empirical noise ```sh git status -s -uall | rg '^\?\?' | rg -v '^\?\? \.gitignore' ``` Cluster untracked paths by top-level directory or extension. **Present clusters to the user and wait for explicit confirmation.** Do not add any empirical pattern without confirmation. ### 5. Compose Run `scripts/compose-gitignore.sh <csv>` to fetch and merge gitignore.io templates. If the network call fails, tell the user and ask whether to continue with bundled-only mode. Append the bundled blocks after the API output in order: ``` # === AI TOOLING === <contents of references/AI-TOOLING.md> # === IDE / EDITOR === <contents of references/IDE-EDITOR.md> # === EMPIRICAL === <user-confirmed patterns, one per line> ``` ### 6. Merge or init - **No existing `.gitignore`**: write the composed output directly. - **Existing `.gitignore`**: merge each `# === SECTION ===` block idempotently — patterns already present in the file are deduplicated (first occurrence wins). Preserve all user content outside section headers. Show the full diff via `difft`; write only after user confirms. ### 7. Verify ```sh git status -s -uall | rg '^\?\?' | wc -l ``` Report untracked count before and after. List any paths still untracked so the user can decide whether to add further patterns. ## Idempotence contract Re-running the skill on a repo where the skill already ran produces no diff. Section headers act as stable merge anchors. User content outside sections is never modified.
Files in this package (5)
- SKILL.md 3 KB
- references/AI-TOOLING.md 1 KB
- references/IDE-EDITOR.md 1 KB
- references/LANGUAGE-DETECTION.md 3 KB
- scripts/compose-gitignore.sh 1 KB
Versions
The database has no other skills named setup-gitignore.
Database snapshot: 13.11.2026 · package version 0494a873d528 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100gitignore-builder
Build and merge .gitignore files using github/gitignore templates with smart project detection. Use when the user asks to "create gitignore", "build .gitignore", "add gitignore templates", "set up gitignore", "update gitignore", or requests "/gitignore". Also trigger when… - 100gitignore
This skill should be used when the user wants to "create a gitignore", "create a .gitignore for X", "update my gitignore", "add entries to gitignore", "ignore this in git", "gitignore for Python/Node/Java/Kotlin/C/Go/Elixir", "mac/windows/linux gitignore entries", or mentions… - 100git-guardrails
Use when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks.… - 100git-guardrails
Use when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks.… - 95git-repo-creator
Put a project on git and GitHub the right way, or audit and fix an existing repository. Covers the repository name, one-line description, public or private, license, .gitignore, README, CI workflow, and, for public repos, the lockdown against outside contributors. Use whenever… - 100new-project
Set up a new project, or bring an existing one without the basics up to standard - personal git identity, CLAUDE.md, tests from day one, CI, README with a status line, .gitignore for secrets. Use when the user starts a new repo or project, says "set up", "bootstrap", "start a…