chore: Update CODEOWNERS to add agentic_dev

[ShawkyZ]

Description

Provide description of this PR and changes, if linked Jira ticket doesn't cover it in full.

Checklist

• Tests added and all succeed
• Regenerated mocks, etc. (make generate)
• Linted (make lint-fix)
• README.md updated, if user-facing
• License file updated, if new 3rd-party dependency is introduced

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @ShawkyZ, 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 introduces a crucial update to the repository's code ownership configuration. By modifying the .github/CODEOWNERS file, it formally designates the @snyk/agentic_dev team as the responsible party for the mcp_extensions/ codebase. This change ensures that future modifications to these files will automatically trigger review requests to the appropriate team, streamlining the review process and maintaining clear accountability.

Highlights

• Code Ownership Update: The CODEOWNERS file has been updated to reflect new team responsibilities.
• New Team Assignment: The @snyk/agentic_dev team has been assigned as code owners for all files within the mcp_extensions/ directory.

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 aims to update the CODEOWNERS file by adding an ownership rule for the mcp_extension directory. My review points out a likely typo in the directory path within the new rule, which would cause it to not function as intended. I've included a code suggestion to correct the path.

[rrama]

@ShawkyZ GH is saying:

Unknown owner: make sure the team @snyk/agentic_dev exists, is publicly visible, and has write access to the repository

Which I am is guessing because the don't have write access. Do we want to give them write access?