What problem does it solve? Choosing the right .gitignore rules for a project is confusing: developers often dump editor and OS noise into committed files, misuse versioned templates, or get contributions to GitHub's gitignore collection rejected for ignoring curation conventions. ## Core Features & Use Cases - Template Selection: Explains the three-tier folder structure (root for evergreen templates, Global/ for editor/OS/tool rules, community/ for specialized and versioned templates) so you pick the right file. - Composition Guidance: Shows how to start from a root template, merge community/ rules for your frameworks, and keep personal editor/OS rules in Git's core.excludesFile instead of the committed file. - Contribution Workflow: Covers the rules for submitting new templates to github/gitignore, including header comments, versioning conventions, and the fork-branch-PR flow. - Use Case: When setting up a new Python project with PyCharm, use this Skill to combine the root Python template with community rules while keeping IDE files in your global ignore. ## Quick Start Ask the AI to help you create a .gitignore for your project by selecting the right templates from GitHub's gitignore collection and deciding which rules belong in the project file versus your global ignore.
