Skip to content

Conversation

robbiemu
Copy link

Reasons for making this change

AI coding assistants have become mainstream development tools in 2025. 41% of code is now AI-generated, and 63% of Professional Developers said they currently use AI in their development process. These tools create various configuration files, cache directories, and session logs that should be excluded from version control to keep repositories clean and avoid committing sensitive API keys or personal settings.

This template addresses the growing need for AI-specific gitignore rules as developers increasingly adopt tools like Cursor, GitHub Copilot, Tabnine, Continue.dev, Aider, and other AI assistants. Many of these tools create local configuration files (like .cursorrules, .aiderignore) and cache directories (like .cursor/, .tabnine/) that are user-specific and shouldn't be shared across teams.

Links to documentation supporting these rule changes

If this is a new template

This extends existing patterns rather than creating a completely new template category, as AI development tools are becoming as common as traditional build tools and IDEs.

I would suggest https://agents.md except I have no prior agreement from them.

Merge and Approval Steps

  • [x ] Confirm that you've read the contribution guidelines and ensured your PR aligns
  • [ N/A? There is only the stale.yml] Ensure CI is passing
  • Get a review and Approval from one of the maintainers

@robbiemu robbiemu requested a review from a team as a code owner August 25, 2025 14:43
@tspader
Copy link

tspader commented Aug 25, 2025

Life is strange. I wanted this exact thing, came to this repository, see a PR had been put up for it half an hour ago. +1.

@robbiemu
Copy link
Author

bumping this little PR -- I am sure you guys will get around to it, but come on, how many PRs here are this relevant? ;)

@rayshan
Copy link
Contributor

rayshan commented Sep 28, 2025

Consider this line Claude Code is adding automatically: **/.claude/settings.local.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants