chore: update repo-map to repo-intel

[avifenesh]

Summary

• Update plugins.json: repo-map -> repo-intel with new description and repo URL
• Update skills.json: repo-mapping -> repo-intel
• Update drift-detect dependency from repo-map to repo-intel

Test Plan

• Site builds and deploys

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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 systematically renames the repo-map plugin and its related skill repo-mapping to repo-intel across the application's configuration files. This change reflects an expansion of the plugin's functionality to encompass unified static analysis, including Git history, AST symbols, and project metadata, beyond just AST symbol and import mapping. All references, including dependencies and descriptions, have been updated to align with the new naming convention and broader scope.

Highlights

• Plugin Renaming: The repo-map plugin has been renamed to repo-intel in plugins.json, along with an updated description, repository URL, and installation command to reflect its expanded capabilities in unified static analysis.
• Dependency Update: The drift-detect plugin's dependency in plugins.json was updated from repo-map to repo-intel.
• Skill Renaming: The repo-mapping skill in skills.json was renamed to repo-intel, and its associated plugin and description were updated.

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.

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 refactors repo-map to repo-intel, updating the plugin and skill definitions. The changes are mostly straightforward, but I've identified a couple of areas for improvement regarding consistency and architectural clarity. Specifically, the new description of repo-intel introduces a potential functional overlap with sync-docs that should be clarified. Additionally, there's a minor inconsistency between the repo-intel plugin and skill descriptions. Please see my detailed comments.

[gemini-code-assist]

The new description for repo-intel mentions 'doc-code sync'. This seems to create a functional overlap with the sync-docs plugin. To clarify the architecture and ensure correct dependency tracking, could you elaborate on the relationship? If repo-intel provides data for sync-docs, it might be beneficial for sync-docs to list repo-intel as a dependency.

[gemini-code-assist]

The description for the repo-intel skill doesn't mention 'doc-code sync', which is part of the repo-intel plugin's description. For consistency and clarity, I suggest aligning the skill's description with the plugin's full capabilities.

Suggested change

	{ "name": "repo-intel", "plugin": "repo-intel", "description": "Unified static analysis - git history, AST symbols, project metadata", "platforms": ["Claude Code", "OpenCode", "Codex"] },
	{ "name": "repo-intel", "plugin": "repo-intel", "description": "Unified static analysis - git history, AST symbols, project metadata, and doc-code sync", "platforms": ["Claude Code", "OpenCode", "Codex"] },