Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Update description exactly per request.
What This Skill Does
Generates .gitignore rules by detecting templates from repository context and fetching patterns from gitignore.io. Updates only a managed block in the existing .gitignore, leaving manually written rules untouched. Re-running is safe and idempotent.
Using gitignore.io templates via a managed block prevents both hand-rolling incomplete rules and accidentally clobbering custom entries on re-runs.
When to use it
- Setting up .gitignore for a new Flutter + Firebase project
- Updating an existing repo's .gitignore after adding a new tool like VS Code
- Regenerating ignore rules without overwriting custom project-specific entries
- Bootstrapping .gitignore in a monorepo with mixed language environments
- Syncing .gitignore patterns when switching CI or adding Docker to a project
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: generate a .gitignore for a Flutter Firebase project with VS Code
- 1Infer templates: flutter, firebase, visualstudiocode from the user prompt
- 2Scan repository files and folders to confirm or add detected templates
- 3Run scripts/update_gitignore.py with --prompt-text and --services flags pointing to the repo root
- 4Script fetches combined rules from toptal.com/developers/gitignore/api/flutter,firebase,visualstudiocode
- 5Script writes the fetched rules into the managed block in .gitignore, preserving any existing custom rules outside the block
.gitignore updated with accurate Flutter, Firebase, and VS Code patterns inside the managed block; custom rules untouched