gitignore

Creates or updates .gitignore files with macOS, VS Code, and detected stack rules.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill gitignore-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitignore
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/gitignore
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill gitignore-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Repositories often ship with missing, inconsistent, or overly broad .gitignore rules, letting cache files, local secrets, and editor artifacts leak into version control. This Skill standardizes .gitignore creation and patching so generated, local, and secret-like files stay out of source control without clobbering existing project rules. ## Core Features & Use Cases - Baseline template: Starts every file from a reusable macOS and VS Code baseline covering .DS_Store, editor temp files, logs, .env files, and common caches. - Stack detection: Inspects markers like package.json, pyproject.toml, go.mod, Cargo.toml, pom.xml, and *.tf to add only relevant Node, Python, Go, Rust, Java/Kotlin, or Terraform ignore rules. - Additive patching: Preserves existing user entries, avoids duplicates, and never adds rules that ignore source code broadly. - Use Case: When scaffolding a new Python and Terraform project, run the Skill to produce a .gitignore that excludes .venv/, pycache/, .terraform/, and *.tfstate while keeping your custom rules intact. ## Quick Start Use the gitignore skill to create or update the .gitignore for this repository based on the detected technology stack.

Frequently Asked Questions about gitignore

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

FAQPage Schema
How do I create a .gitignore for a new project?

Run the gitignore skill in the repository root. It starts from a macOS and VS Code baseline template, detects your stack from marker files like package.json or go.mod, and writes a grouped .gitignore with only relevant rules.

How do I add missing rules to an existing .gitignore without losing my entries?

The skill patches the existing file additively: it keeps all user and custom entries, appends only missing standard patterns, and avoids duplicates so re-running produces no churn.

Which technology stacks does the gitignore skill detect?

It detects Node via package.json and lockfiles, Python via pyproject.toml or requirements.txt, Go via go.mod, Rust via Cargo.toml, Java/Kotlin via pom.xml or Gradle files, and Terraform via *.tf or .terraform.lock.hcl.

Does the gitignore skill ignore source files or Cargo.lock?

No. It never adds broad rules that ignore source code such as src/ or *.py, and it keeps Cargo.lock tracked unless you explicitly ask to ignore it. Only caches, build outputs, logs, and secret-like files are excluded.

Why does my .gitignore keep letting .env files into commits?

Your .gitignore likely lacks environment file patterns. The skill's baseline adds .env and .env.* while whitelisting .env.example, keeping local secrets out of source control while preserving shareable templates.