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.