chore: update .gitignore with popular vibe-coding agent directories

[vitali87]

Add .roo/, .augment, and .vscode to .gitignore for popular vibe-coding agents.

Dependency graph

Merge in this order:

pr-1: chore: update .gitignore with popular vibe-coding agent directories  <-- this PR
pr-2: fix(llm): add retries to RAG orchestrator to handle output validation issues
├── pr-4: feat(mcp/tools): add shell_command, document_analyzer, semantic_search, and ask_agent tools to MCP registry
│   └── pr-5: feat(mcp/client): add MCP client CLI for querying the code graph via MCP server
│       └── pr-7: docs: update README with non-interactive mode, new MCP tools, and agent tool list
└── pr-6: feat(main): add non-interactive --ask-agent mode to the CLI
    └── pr-7: docs: update README with non-interactive mode, new MCP tools, and agent tool list
pr-3: feat(mcp/server): improve MCP server logging and suppress output during tool execution
└── pr-4: feat(mcp/tools): add shell_command, document_analyzer, semantic_search, and ask_agent tools to MCP registry
    └── pr-5: feat(mcp/client): add MCP client CLI for querying the code graph via MCP server
        └── pr-7: docs: update README with non-interactive mode, new MCP tools, and agent tool list

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the developer experience by updating the .gitignore file. The changes prevent common agent-generated files and IDE-specific configurations from being tracked by version control, ensuring a cleaner repository and reducing potential conflicts or unnecessary commits.

Highlights

• .gitignore Update: Added new entries to the .gitignore file to exclude directories commonly generated by popular vibe-coding agents, specifically .roo/, .augment, and .vscode.

Changelog

• .gitignore
  • Added '.roo/' to ignore directories created by certain agents.
  • Added '.augment' to ignore directories created by certain agents.
  • Added '.vscode' to ignore VS Code-related configuration and temporary files.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the .gitignore file to add entries for directories used by popular "vibe-coding agents". The change is straightforward. I've added one suggestion to improve the precision of the new gitignore patterns by explicitly marking directory paths with a trailing slash, which is a common best practice.

[gemini-code-assist]

To make the .gitignore patterns more precise, it's recommended to add a trailing slash to entries that represent directories. This prevents git from ignoring a file that might have the same name. Since .augment and .vscode are directories, adding a slash would be a good improvement.

.augment/
.vscode/

[greptile-apps]

Greptile Summary

Added ignore patterns for three popular vibe-coding agent directories (.roo/, .augment, .vscode) to prevent these tools' configuration from being committed.

• Added .roo/ for Roo coding agent
• Added .augment for Augment Code agent
• Added .vscode for VS Code workspace settings
• Minor style inconsistency: .augment and .vscode should use trailing slashes to match existing directory pattern

Confidence Score: 4/5

• This PR is safe to merge with minimal risk - it only modifies .gitignore
• Simple configuration change with no functional impact. Only minor style inconsistency with trailing slashes that should be addressed for consistency with existing patterns.
• No files require special attention

Important Files Changed

Filename	Overview
.gitignore	Added three vibe-coding agent directories to gitignore; minor style inconsistency with trailing slashes

_{Last reviewed commit: c0a9cb5}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Inconsistent trailing slashes - .augment and .vscode should have trailing slashes to match the pattern used for other directories in this file (.ruff_cache/, .claude/, etc.)

Suggested change

	.augment
	.vscode
	.augment/
	.vscode/

Prompt To Fix With AI

This is a comment left during a code review.
Path: .gitignore
Line: 21-22

Comment:
Inconsistent trailing slashes - `.augment` and `.vscode` should have trailing slashes to match the pattern used for other directories in this file (`.ruff_cache/`, `.claude/`, etc.)

```suggestion
.augment/
.vscode/
```

How can I resolve this? If you propose a fix, please make it concise.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}