seeding-gitignore

Creates and edits .gitignore files with a fixed baseline plus project-derived language patterns.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill seeding-gitignore-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seeding-gitignore
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/seeding-gitignore
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill seeding-gitignore-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repositories accumulate OS noise, editor swap files, local agent-tooling state, and build artifacts that should never be committed. This Skill seeds and maintains .gitignore files so local artifacts are ignored before they get staged, while keeping shared configuration like most of .claude/ tracked. ## Core Features & Use Cases - Fixed baseline: Applies a verbatim baseline covering OS noise (.DS_Store, Thumbs.db), editor swap files, per-developer Claude Code files, local agent-tooling state (.superpowers/, .agentsroom/, Playwright output), and git worktree directories. - Project-derived patterns: Inspects manifests and lockfiles (package.json, Cargo.toml, pyproject.toml, go.mod) to add only the ignore patterns the project's actual stack produces, using canonical github/gitignore templates. - Pre-commit guard: Reviews git status --short before commits, adds missing patterns, and untracks already-committed artifacts with git rm --cached. - Use Case: After running git init on a new Node project, the Skill writes the baseline, adds node_modules/ and dist/ based on package.json, and leaves the rest of .claude/ committed. ## Quick Start Ask the assistant to seed or update the .gitignore for this repository before committing, ignoring local artifacts and tool output based on what the project uses.

Frequently Asked Questions about seeding-gitignore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a .gitignore for a new git repository?▼

Start with a fixed baseline covering OS noise, editor swap files, and local tooling state, then inspect the project's manifests like package.json or Cargo.toml to add the dependency directories and build output that stack actually produces.

How to stop committing .DS_Store and other OS files to git?▼

Add OS-level patterns such as .DS_Store, Thumbs.db, and desktop.ini to .gitignore. If the files are already tracked, untrack them with git rm --cached in the same commit so the ignore rule takes effect.

Should .claude/ directory be gitignored in Claude Code projects?▼

Only per-developer files should be ignored: CLAUDE.local.md, .claude/settings.local.json, .claude/*.local.json, and scheduled task files. Everything else under .claude/ stays committed, so never blanket-ignore the whole directory.

Why is a file still tracked after adding it to .gitignore?▼

Git keeps tracking files that were committed before the ignore pattern was added. Run git rm --cached <path> to untrack the file while keeping it on disk, then commit the change alongside the new .gitignore entry.

Should Playwright test artifacts and screenshots be committed?▼

Reference snapshots used as visual test expectations belong in git, but reports, videos, traces, and -actual/-diff images from failed runs do not. Classify by what a path holds, not where it sits, since runners may nest output inside reference directories.