feat(plugins): Add repository-explorer plugin for AI-powered codebase analysis#908
feat(plugins): Add repository-explorer plugin for AI-powered codebase analysis#908
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. WalkthroughThis PR introduces a new "repository-explorer" AI-powered plugin for codebase analysis, bumps the marketplace and repomix-commands plugin versions to 1.0.2, adds output analysis guidance to existing command documentation, and updates user guides across 12 languages plus the root README. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~20 minutes The changes are predominantly repetitive (same pattern applied across 12 language documentation files), configuration-driven (version bumps, metadata additions), and low in logic complexity. While the file count is substantial (~18 files), the homogeneity of updates reduces per-file cognitive overhead. New plugin documentation is procedural and instructional rather than algorithmically complex. Possibly related PRs
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello @yamadashy, I'm Gemini Code Assist1! 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 significant enhancement to the Claude Code plugin ecosystem by adding the Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Pull Request Overview
Adds a new repository-explorer plugin providing AI-assisted local and remote repository analysis using Repomix CLI, plus documentation and marketplace/version updates.
- Introduces repository-explorer agent, commands, and marketplace registration.
- Updates multilingual documentation and README to include usage and installation instructions.
- Enhances repomix-commands docs with guidance for delegating large output analysis to sub-agents and bumps versions.
Reviewed Changes
Copilot reviewed 21 out of 21 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| .claude/plugins/repository-explorer/agents/repository-explorer.md | Adds comprehensive agent instructions and workflow for repository analysis. |
| .claude/plugins/repository-explorer/commands/explore-local.md | Defines local exploration command usage and task template. |
| .claude/plugins/repository-explorer/commands/explore-remote.md | Defines remote exploration command usage and task template. |
| .claude/plugins/repository-explorer/.claude-plugin/plugin.json | Declares new plugin metadata. |
| .claude/plugins/repomix-commands/commands/pack-local.md | Adds guidance for delegating analysis to sub-agents to avoid large context consumption. |
| .claude/plugins/repomix-commands/commands/pack-remote.md | Adds output analysis delegation instructions. |
| .claude/plugins/repomix-commands/.claude-plugin/plugin.json | Version bump to 1.0.2. |
| .claude-plugin/marketplace.json | Registers new plugin and updates marketplace version. |
| README.md | Documents new repository-explorer plugin with features and usage. |
| website/client/src/en/guide/claude-code-plugins.md | English docs updated with repository-explorer section and examples. |
| website/client/src/ja/guide/claude-code-plugins.md | Japanese docs updated with plugin description and examples. |
| website/client/src/zh-cn/guide/claude-code-plugins.md | Simplified Chinese docs updated for new plugin. |
| website/client/src/zh-tw/guide/claude-code-plugins.md | Traditional Chinese docs updated for new plugin. |
| website/client/src/es/guide/claude-code-plugins.md | Spanish docs updated for new plugin. |
| website/client/src/fr/guide/claude-code-plugins.md | French docs updated for new plugin. |
| website/client/src/de/guide/claude-code-plugins.md | German docs updated for new plugin. |
| website/client/src/pt-br/guide/claude-code-plugins.md | Brazilian Portuguese docs updated for new plugin. |
| website/client/src/hi/guide/claude-code-plugins.md | Hindi docs updated for new plugin. |
| website/client/src/id/guide/claude-code-plugins.md | Indonesian docs updated for new plugin. |
| website/client/src/vi/guide/claude-code-plugins.md | Vietnamese docs updated for new plugin. |
| website/client/src/ko/guide/claude-code-plugins.md | Korean docs updated for new plugin. |
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
Deploying repomix with
|
| Latest commit: |
308c5cc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://66f7aea8.repomix.pages.dev |
| Branch Preview URL: | https://feat-repomix-explore-agent-p.repomix.pages.dev |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #908 +/- ##
==========================================
+ Coverage 73.55% 74.60% +1.05%
==========================================
Files 111 111
Lines 7782 7782
Branches 1472 1450 -22
==========================================
+ Hits 5724 5806 +82
+ Misses 2058 1976 -82 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new repository-explorer plugin for AI-powered codebase analysis, which is a great addition. The changes are comprehensive, including the plugin definition, new slash commands, and extensive documentation updates across 12 languages.
My review focuses on the new agent definition. I've found a critical issue in the YAML frontmatter that would likely cause parsing to fail, and a medium-severity issue where the agent's communication language is hardcoded to Japanese, which could be problematic for international users.
Overall, this is a well-structured feature addition. Once these two points are addressed, it should be ready to merge.
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
Code Review - PR #908: repository-explorer PluginHi @yamadashy! Overall this is a well-structured addition. Rating: 8.5/10 Strengths
Must Fix Before Merge
Should Fix
Potential Issues Found
Premortem Scenarios
Minor Issues
Recommendation: Approve with changes. Excellent work on documentation! Once tests are added and critical issues addressed, this will be a great addition. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (2)
.claude/plugins/repomix-commands/commands/pack-remote.md (1)
72-98: Excellent context-management guidance that aligns well with the new repository-explorer plugin.This section effectively addresses a real pain point: large repomix outputs consuming excessive context. The workflow is clear, the agent-selection strategy is sensible (prioritizing repository-explorer with sensible fallbacks), and the concrete example is actionable.
One minor style refinement: consider replacing "very large" (line 74) with a more specific descriptor like "substantial" or "potentially large" to avoid the overused intensifier.
Suggested refinement (optional):
-**IMPORTANT**: The generated output file can be very large and consume significant context. +**IMPORTANT**: The generated output file can be substantial and consume significant context..claude/plugins/repository-explorer/commands/explore-remote.md (1)
7-7: Consider stronger wording for the opening statement.The phrasing "they want to explore" is acceptable but somewhat vague. The static analysis tool suggests considering alternatives to strengthen the intent.
For example, you could rephrase to:
When the user runs this command, they aim to explore and understand a remote repository's code structure, patterns, and content.This is optional and a matter of style preference.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (21)
.claude-plugin/marketplace.json(2 hunks).claude/plugins/repomix-commands/.claude-plugin/plugin.json(1 hunks).claude/plugins/repomix-commands/commands/pack-local.md(1 hunks).claude/plugins/repomix-commands/commands/pack-remote.md(1 hunks).claude/plugins/repository-explorer/.claude-plugin/plugin.json(1 hunks).claude/plugins/repository-explorer/agents/repository-explorer.md(1 hunks).claude/plugins/repository-explorer/commands/explore-local.md(1 hunks).claude/plugins/repository-explorer/commands/explore-remote.md(1 hunks)README.md(2 hunks)website/client/src/de/guide/claude-code-plugins.md(4 hunks)website/client/src/en/guide/claude-code-plugins.md(4 hunks)website/client/src/es/guide/claude-code-plugins.md(4 hunks)website/client/src/fr/guide/claude-code-plugins.md(4 hunks)website/client/src/hi/guide/claude-code-plugins.md(4 hunks)website/client/src/id/guide/claude-code-plugins.md(4 hunks)website/client/src/ja/guide/claude-code-plugins.md(4 hunks)website/client/src/ko/guide/claude-code-plugins.md(4 hunks)website/client/src/pt-br/guide/claude-code-plugins.md(4 hunks)website/client/src/vi/guide/claude-code-plugins.md(4 hunks)website/client/src/zh-cn/guide/claude-code-plugins.md(4 hunks)website/client/src/zh-tw/guide/claude-code-plugins.md(4 hunks)
🧰 Additional context used
🪛 LanguageTool
website/client/src/fr/guide/claude-code-plugins.md
[grammar] ~25-~25: « analyse » semble plus probable dans ce contexte
Context: ...## 3. repository-explorer (Plugin Agent d'Analyse IA) Agent d'analyse de dépôt alimenté par...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~25-~25: Il y a peut-être une erreur ici
Context: ...ory-explorer (Plugin Agent d'Analyse IA) Agent d'analyse de dépôt alimenté par l'...
(QB_NEW_FR)
[style] ~27-~27: Une autre structure plus directe dynamisera votre phrase.
Context: ...xplore intelligemment les bases de code en utilisant Repomix CLI. Fonctionnalités : - E...
(EN_UTILISANT)
[grammar] ~27-~27: Il y a peut-être une erreur ici
Context: ... bases de code en utilisant Repomix CLI. Fonctionnalités : - Exploration et ana...
(QB_NEW_FR)
[style] ~30-~30: Cette structure peut être modifiée afin de devenir plus percutante.
Context: ...ionnalités :** - Exploration et analyse de base de code en langage naturel - Découverte...
(DE_BASE3)
[grammar] ~33-~33: Il y a peut-être une erreur ici
Context: ...tique du contexte pour les grands dépôts Commandes Disponibles : - `/repository...
(QB_NEW_FR)
[typographical] ~35-~35: Le trait d’union est employé sans espaces pour former des mots, alors que le tiret est encadré par des espaces et placé entre deux mots distincts.
Context: ... grands dépôts Commandes Disponibles : - /repository-explorer:explore-local - Analyser une base de code locale avec a...
(TIRET)
[grammar] ~36-~36: Envisagez un remplacement
Context: ...- Analyser une base de code locale avec assistance IA - /repository-explorer:explore-remote - Analyser des dépôts GitHub distants avec assista...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_SPACE_
_DASH_PERIOD
–)
[grammar] ~37-~37: Élément manquant
Context: ...nalyser des dépôts GitHub distants avec assistance IA Fonctionnement : 1. Exécute `npx repom...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~40-~40: Élément manquant
Context: ...npx repomix@latest pour empaqueter le dépôt 2. Utilise les outils Grep et Read pour...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~41-~41: Élément manquant
Context: ...et Read pour rechercher efficacement la sortie 3. Fournit une analyse complète sans co...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~42-~42: Il y a peut-être une erreur ici
Context: ...lète sans consommer de contexte excessif ## Installation ### 1. Ajouter le Marketpl...
(QB_NEW_FR)
[grammar] ~69-~69: « tip » semble plus probable dans ce contexte
Context: ...ll repository-explorer@repomix ``` ::: tip Relations entre Plugins Le plugin `repo...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)
[grammar] ~69-~69: « plugins » semble plus probable dans ce contexte
Context: ...er@repomix ``` ::: tip Relations entre Plugins Le plugin repomix-mcp est recommandé ...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[style] ~70-~70: L’adverbe précède le verbe à l’infinitif.
Context: ...entées par l'IA. Bien que vous puissiez les installer indépendamment, utiliser les trois offre l'expérience ...
(PLACE_DE_L_ADVERBE)
[grammar] ~70-~70: Il y a peut-être une erreur ici
Context: ...ois offre l'expérience la plus complète. ::: ### Alternative : Installation Inte...
(QB_NEW_FR)
[grammar] ~113-~113: « base » semble plus probable dans ce contexte
Context: ...ertoires spécifiques" ### Explorer une Base de Code Locale avec l'IA Utilisez la c...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~113-~113: « code locale » semble plus probable dans ce contexte
Context: ... spécifiques" ### Explorer une Base de Code Locale avec l'IA Utilisez la commande ...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~113-~113: « code locale » semble plus probable dans ce contexte
Context: ...ifiques" ### Explorer une Base de Code Locale avec l'IA Utilisez la commande `/repos...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~113-~113: Il y a peut-être une erreur ici
Context: ...plorer une Base de Code Locale avec l'IA Utilisez la commande `/repository-explor...
(QB_NEW_FR)
[typographical] ~115-~115: Une espace est requise.
Context: ... Locale avec l'IA Utilisez la commande /repository-explorer:explore-local pour une analyse alimenté...
(DEUX_POINTS_ESPACE)
[grammar] ~115-~115: Il y a peut-être une erreur ici
Context: ...e-local` pour une analyse alimentée par l'IA : text /repository-explorer:explore-local ./src Trouver tout le code lié à l'authentification Autres exemples : - "Analyser la structu...
(QB_NEW_FR)
[grammar] ~125-~125: Il y a peut-être une erreur ici
Context: ...ux" - "Trouver tous les endpoints d'API" ### Explorer un Dépôt Distant avec l'IA Uti...
(QB_NEW_FR)
[grammar] ~127-~127: « dépôt distant » semble plus probable dans ce contexte
Context: ...s les endpoints d'API" ### Explorer un Dépôt Distant avec l'IA Utilisez la commande...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~127-~127: « dépôt distant » semble plus probable dans ce contexte
Context: ...endpoints d'API" ### Explorer un Dépôt Distant avec l'IA Utilisez la commande `/repos...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~127-~127: Il y a peut-être une erreur ici
Context: ... ### Explorer un Dépôt Distant avec l'IA Utilisez la commande `/repository-explor...
(QB_NEW_FR)
[typographical] ~129-~129: Une espace est requise.
Context: ...Distant avec l'IA Utilisez la commande /repository-explorer:explore-remote pour analyser des dépôts...
(DEUX_POINTS_ESPACE)
[grammar] ~129-~129: Il y a peut-être une erreur ici
Context: ...xplore-remote` pour analyser des dépôts GitHub : text /repository-explorer:explore-remote facebook/react Me montrer l'architecture des composants principaux Autres exemples : - "Trouver tous les ho...
(QB_NEW_FR)
[grammar] ~139-~139: Vérifiez l’accord du participe passé avec le sujet inversé
Context: ...quer la structure du projet" - "Où sont définis les limites d'erreur ?" ## Ressources ...
(QB_NEW_FR_OTHER_ERROR_IDS_VPPA_SUJET_INVERSE_6)
[grammar] ~139-~139: Il y a peut-être une erreur ici
Context: ... projet" - "Où sont définis les limites d'erreur ?" ## Ressources Connexes - [Documentation du...
(QB_NEW_FR)
[grammar] ~155-~155: « dépôt » semble plus probable dans ce contexte
Context: ...omix-commands) - Plugin Explorateur de Dépôt ## Retours et Support Si vous rencontrez d...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
website/client/src/hi/guide/claude-code-plugins.md
[grammar] ~25-~25: Il y a peut-être une erreur ici
Context: ...tory-explorer (AI विश्लेषण एजेंट प्लगइन) AI-संचालित रिपॉजिटरी विश्लेषण एजेंट जो R...
(QB_NEW_FR)
[grammar] ~27-~27: Il y a peut-être une erreur ici
Context: ...ग करके कोडबेस को बुद्धिमानी से खोजता है। विशेषताएं: - प्राकृतिक भाषा में कोडबेस...
(QB_NEW_FR)
[grammar] ~29-~29: « विशेषताएँ : » semble plus probable dans ce contexte
Context: ...के कोडबेस को बुद्धिमानी से खोजता है। विशेषताएं: - प्राकृतिक भाषा में कोडबेस की खोज और...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_DIACRITIC)
[grammar] ~30-~30: Essayez de remplacer cet élément par « langue »
Context: ...े खोजता है। विशेषताएं: - प्राकृतिक भाषा में कोडबेस की खोज और विश्लेषण - बुद्धिम...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~33-~33: Il y a peut-être une erreur ici
Context: ...रिपॉजिटरी के लिए स्वचालित संदर्भ प्रबंधन उपलब्ध कमांड: - `/repository-explorer:...
(QB_NEW_FR)
[typographical] ~35-~35: Le trait d’union est employé sans espaces pour former des mots, alors que le tiret est encadré par des espaces et placé entre deux mots distincts.
Context: ... स्वचालित संदर्भ प्रबंधन उपलब्ध कमांड: - /repository-explorer:explore-local - AI सहायता के साथ स्थानीय कोडबेस का विश्...
(TIRET)
[grammar] ~36-~36: Envisagez un remplacement
Context: ...ा के साथ स्थानीय कोडबेस का विश्लेषण करें - /repository-explorer:explore-remote - AI सहायता के साथ दूरस्थ GitHub रिपॉजिटरी क...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_SPACE_
_DASH_PERIOD
–)
[grammar] ~37-~37: Il y a peut-être une erreur ici
Context: ...दूरस्थ GitHub रिपॉजिटरी का विश्लेषण करें कैसे काम करता है: 1. रिपॉजिटरी को पैक ...
(QB_NEW_FR)
[grammar] ~40-~40: Élément manquant
Context: ... करने के लिए npx repomix@latest चलाता है 2. आउटपुट को कुशलता से खोजने के लिए Gre...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_।)
[grammar] ~41-~41: Élément manquant
Context: ...े के लिए Grep और Read टूल का उपयोग करता है 3. अत्यधिक संदर्भ का उपभोग किए बिना व्य...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_।)
[grammar] ~42-~42: Élément manquant
Context: ...ोग किए बिना व्यापक विश्लेषण प्रदान करता है ## इंस्टॉलेशन ### 1. Repomix प्लगइन मार्के...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_।)
[grammar] ~68-~68: Essayez d’enlever « tip »
Context: ...nstall repository-explorer@repomix ``` ::: tip प्लगइन संबंध repomix-mcp प्लगइन को आधार के र...
(QB_NEW_FR_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[style] ~70-~70: Un mot est répété.
Context: ...ाएं जोड़ता है। हालांकि आप उन्हें स्वतंत्र रूप से इंस्टॉल कर सकते हैं, तीनों का उपयो...
(FRENCH_WORD_REPEAT_RULE)
[grammar] ~113-~113: Il y a peut-être une erreur ici
Context: ...### AI के साथ स्थानीय कोडबेस की खोज करें AI-संचालित विश्लेषण के लिए `/repository-...
(QB_NEW_FR)
[typographical] ~115-~115: Une espace est requise.
Context: ...की खोज करें AI-संचालित विश्लेषण के लिए /repository-explorer:explore-local कमांड का उपयोग करें: ```...
(DEUX_POINTS_ESPACE)
[grammar] ~115-~115: Il y a peut-être une erreur ici
Context: ...orer:explore-local` कमांड का उपयोग करें: text /repository-explorer:explore-local ./src सभी प्रमाणीकरण संबंधी कोड खोजें अन्य उदाहरण: - "इस प्रोजेक्ट की संरचना क...
(QB_NEW_FR)
[grammar] ~127-~127: Il y a peut-être une erreur ici
Context: ...# AI के साथ दूरस्थ रिपॉजिटरी की खोज करें GitHub रिपॉजिटरी का विश्लेषण करने के लिए...
(QB_NEW_FR)
[typographical] ~129-~129: Une espace est requise.
Context: ...itHub रिपॉजिटरी का विश्लेषण करने के लिए /repository-explorer:explore-remote कमांड का उपयोग करें: ``...
(DEUX_POINTS_ESPACE)
[grammar] ~129-~129: Il y a peut-être une erreur ici
Context: ...rer:explore-remote` कमांड का उपयोग करें: text /repository-explorer:explore-remote facebook/react मुझे मुख्य घटक आर्किटेक्चर दिखाएं अन्य उदाहरण: - "रिपॉजिटरी में सभी React ...
(QB_NEW_FR)
[grammar] ~136-~136: Typographie
Context: ... मुख्य घटक आर्किटेक्चर दिखाएं ``` अन्य उदाहरण: - "रिपॉजिटरी में सभी React हुक खोजें" -...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~137-~137: Élément manquant
Context: ... उदाहरण: - "रिपॉजिटरी में सभी React हुक खोजें" - "प्रोजेक्ट संरचना की व्याख्या करें" -...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~138-~138: Élément manquant
Context: ... खोजें" - "प्रोजेक्ट संरचना की व्याख्या करें" - "त्रुटि सीमाएं कहां परिभाषित हैं?" #...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~139-~139: Typographie
Context: ...या करें" - "त्रुटि सीमाएं कहां परिभाषित हैं?" ## संबंधित संसाधन - [MCP सर्वर दस्तावेज़ीक...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~155-~155: Il y a peut-être une erreur ici
Context: ...commands) - रिपॉजिटरी एक्सप्लोरर प्लगइन ## फीडबैक और सहायता यदि आपको समस्याएं आती ...
(QB_NEW_FR)
website/client/src/de/guide/claude-code-plugins.md
[grammar] ~25-~25: Hier könnte ein Fehler sein.
Context: ...itory-explorer (KI-Analyse-Agent-Plugin) KI-gesteuerter Repository-Analyse-Agent,...
(QB_NEW_DE)
[grammar] ~27-~27: Korrigiere das Wort
Context: ...steuerter Repository-Analyse-Agent, der Codebases intelligent mit Repomix CLI erkundet. ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[grammar] ~27-~27: Hier könnte ein Fehler sein.
Context: ...es intelligent mit Repomix CLI erkundet. Funktionen: - Natürlichsprachliche Cod...
(QB_NEW_DE)
[grammar] ~33-~33: Hier könnte ein Fehler sein.
Context: ...Kontextverwaltung für große Repositories Verfügbare Befehle: - `/repository-exp...
(QB_NEW_DE)
[grammar] ~35-~35: Korrigiere die Fehler
Context: ...roße Repositories Verfügbare Befehle: - /repository-explorer:explore-local - Lokale Codebase mit KI-Unterstützung an...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~36-~36: Entferne das Symbol
Context: ...odebase mit KI-Unterstützung analysieren - /repository-explorer:explore-remote - Entfernte GitHub-Repositories mit KI-Un...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_OTHER)
[grammar] ~37-~37: Hier könnte ein Fehler sein.
Context: ...itories mit KI-Unterstützung analysieren Funktionsweise: 1. Führt `npx repomix@...
(QB_NEW_DE)
[grammar] ~42-~42: Hier könnte ein Fehler sein.
Context: ...nalyse ohne übermäßigen Kontextverbrauch ## Installation ### 1. Repomix-Plugin-Mark...
(QB_NEW_DE)
[grammar] ~70-~70: Hier könnte ein Fehler sein.
Context: ...g aller drei die umfassendste Erfahrung. ::: ### Alternative: Interaktive Instal...
(QB_NEW_DE)
[grammar] ~113-~113: Hier könnte ein Fehler sein.
Context: ...en" ### Lokale Codebase mit KI erkunden Verwenden Sie den Befehl `/repository-ex...
(QB_NEW_DE)
[grammar] ~115-~115: Hier könnte ein Fehler sein.
Context: ...explore-local` für KI-gestützte Analyse: text /repository-explorer:explore-local ./src Alle authentifizierungsbezogenen Codes finden Weitere Beispiele: - "Die Struktur diese...
(QB_NEW_DE)
[grammar] ~123-~123: Ersetze das Satzzeichen
Context: ... Codes finden ``` Weitere Beispiele: - "Die Struktur dieses Projekts analysieren" -...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~123-~123: Ersetze das Satzzeichen
Context: ...spiele: - "Die Struktur dieses Projekts analysieren" - "Die Hauptkomponenten anzeigen" - "Al...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~124-~124: Ersetze das Satzzeichen
Context: ...Struktur dieses Projekts analysieren" - "Die Hauptkomponenten anzeigen" - "Alle API-...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~124-~124: Ersetze das Satzzeichen
Context: ...ts analysieren" - "Die Hauptkomponenten anzeigen" - "Alle API-Endpunkte finden" ### Entf...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~125-~125: Ersetze das Satzzeichen
Context: ...en" - "Die Hauptkomponenten anzeigen" - "Alle API-Endpunkte finden" ### Entferntes R...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~125-~125: Ersetze das Satzzeichen
Context: ...onenten anzeigen" - "Alle API-Endpunkte finden" ### Entferntes Repository mit KI erkunden V...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~127-~127: Hier könnte ein Fehler sein.
Context: ...## Entferntes Repository mit KI erkunden Verwenden Sie den Befehl `/repository-ex...
(QB_NEW_DE)
[grammar] ~129-~129: Hier könnte ein Fehler sein.
Context: ..., um GitHub-Repositories zu analysieren: text /repository-explorer:explore-remote facebook/react Die Hauptkomponentenarchitektur anzeigen Weitere Beispiele: - "Alle React-Hooks i...
(QB_NEW_DE)
[grammar] ~137-~137: Ersetze das Satzzeichen
Context: ...ktur anzeigen ``` Weitere Beispiele: - "Alle React-Hooks im Repository finden" - "Di...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~137-~137: Ersetze das Satzzeichen
Context: ...iele: - "Alle React-Hooks im Repository finden" - "Die Projektstruktur erklären" - "Wo ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~138-~138: Ersetze das Satzzeichen
Context: ...lle React-Hooks im Repository finden" - "Die Projektstruktur erklären" - "Wo sind Er...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~138-~138: Ersetze das Satzzeichen
Context: ...pository finden" - "Die Projektstruktur erklären" - "Wo sind Error Boundaries definiert?"...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~139-~139: Ersetze das Satzzeichen
Context: ...den" - "Die Projektstruktur erklären" - "Wo sind Error Boundaries definiert?" ## V...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~139-~139: Ersetze das Satzzeichen
Context: ...r erklären" - "Wo sind Error Boundaries definiert?" ## Verwandte Ressourcen - [MCP-Server-Doku...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~155-~155: Hier könnte ein Fehler sein.
Context: ...-commands) - Repository-Explorer-Plugin ## Feedback und Support Wenn Sie Probleme ...
(QB_NEW_DE)
website/client/src/pt-br/guide/claude-code-plugins.md
[uncategorized] ~69-~69: Pontuação duplicada
Context: ...stall repository-explorer@repomix ``` ::: tip Relação entre Plugins O plugin `rep...
(DOUBLE_PUNCTUATION_XML)
.claude/plugins/repository-explorer/commands/explore-local.md
[style] ~7-~7: Consider using an alternative to strengthen your wording.
Context: ... When the user runs this command, they want to explore and understand a local proje...
(WANT_KEEN)
.claude/plugins/repomix-commands/commands/pack-local.md
[style] ~67-~67: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ANT**: The generated output file can be very large and consume significant context. If th...
(EN_WEAK_ADJECTIVE)
[style] ~95-~95: Consider using a more formal alternative.
Context: ... ## Help and Documentation If you need more information about available options or encounter an...
(MORE_INFO)
.claude/plugins/repomix-commands/commands/pack-remote.md
[style] ~74-~74: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ANT**: The generated output file can be very large and consume significant context. If th...
(EN_WEAK_ADJECTIVE)
[style] ~102-~102: Consider using a more formal alternative.
Context: ... ## Help and Documentation If you need more information about available options or encounter an...
(MORE_INFO)
website/client/src/es/guide/claude-code-plugins.md
[style] ~25-~25: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ... de GitHub ### 3. repository-explorer (Plugin de Agente de Análisis de IA) Agente de...
(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGIN)
[uncategorized] ~30-~30: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...s de bases de código en lenguaje natural - Descubrimiento inteligente de patrones y...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~31-~31: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ... comprensión de la estructura del código - Análisis incremental usando grep y lectu...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~32-~32: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...o grep y lectura de archivos específicos - Gestión automática de contexto para repo...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[typographical] ~35-~35: Mayúsculas y minúsculas recomendadas.
Context: ...o para repositorios grandes Comandos Disponibles: - `/repository-explorer:explore-loca...
(AI_ES_GGEC_REPLACEMENT_CASING_UPPERCASE)
[uncategorized] ~40-~40: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...x@latest` para empaquetar el repositorio 2. Usa herramientas Grep y Read para buscar...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~41-~41: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ead para buscar eficientemente la salida 3. Proporciona análisis integral sin consum...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~69-~69: El sustantivo empleado no parece adecuado en este contexto. Considere una alternativa.
Context: ...rer@repomix ``` ::: tip Relación entre Plugins El plugin repomix-mcp se recomienda c...
(AI_ES_GGEC_REPLACEMENT_NOUN)
[style] ~70-~70: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ... ``` ::: tip Relación entre Plugins El plugin repomix-mcp se recomienda como base. ...
(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGIN)
[style] ~70-~70: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ...epomix-mcpse recomienda como base. El pluginrepomix-commands` proporciona comandos...
(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGIN)
[uncategorized] ~70-~70: La forma del verbo empleada no parece la adecuada en este contexto. Considere una alternativa.
Context: ...s de análisis impulsadas por IA. Aunque puede instalarlos independientemente, usar lo...
(AI_ES_GGEC_REPLACEMENT_VERB_FORM)
[uncategorized] ~114-~114: Posible confusión. Considere aplicar la sugerencia.
Context: ...# Explorar Base de Código Local con IA Use el comando `/repository-explorer:explor...
(AI_ES_GGEC_REPLACEMENT_CONFUSION)
[uncategorized] ~115-~115: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...re-local` para análisis impulsado por IA: ```text /repository-explorer:explore-l...
(AI_ES_GGEC_REPLACEMENT_PUNCTUATION)
[uncategorized] ~129-~129: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...te` para analizar repositorios de GitHub: ```text /repository-explorer:explore-r...
(AI_ES_GGEC_REPLACEMENT_PUNCTUATION)
[style] ~155-~155: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ...in/.claude/plugins/repomix-commands) - [Plugin Explorador de Repositorios](https://git...
(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGIN)
website/client/src/ko/guide/claude-code-plugins.md
[grammar] ~25-~25: Il y a peut-être une erreur ici
Context: ...3. repository-explorer (AI 분석 에이전트 플러그인) Repomix CLI를 사용하여 코드베이스를 지능적으로 탐색하는 AI 기...
(QB_NEW_FR)
[grammar] ~27-~27: Il y a peut-être une erreur ici
Context: ... 코드베이스를 지능적으로 탐색하는 AI 기반 저장소 분석 에이전트입니다. 기능: - 자연어를 사용한 코드베이스 탐색 및 분석 - 지능적인 패턴...
(QB_NEW_FR)
[grammar] ~35-~35: Essayez « commandes disponibles :
– »
Context: ...를 사용한 점진적 분석 - 대형 저장소를 위한 자동 컨텍스트 관리 사용 가능한 명령: - `/repository-explorer:explo...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[typographical] ~35-~35: Le trait d’union est employé sans espaces pour former des mots, alors que le tiret est encadré par des espaces et placé entre deux mots distincts.
Context: ... 분석 - 대형 저장소를 위한 자동 컨텍스트 관리 사용 가능한 명령: - /repository-explorer:explore-local - AI 지원으로 로컬 코드베이스 분석 - `/repository-expl...
(TIRET)
[grammar] ~36-~36: Envisagez un remplacement
Context: ...rer:explore-local- AI 지원으로 로컬 코드베이스 분석 -/repository-explorer:explore-remote- AI 지원으로 원격 GitHub 저장소 분석 **작동 방식:** 1.n...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_SPACE_
_DASH_PERIOD
–)
[grammar] ~37-~37: Il y a peut-être une erreur ici
Context: ...plore-remote- AI 지원으로 원격 GitHub 저장소 분석 **작동 방식:** 1.npx repomix@latest`를 실행하여 저...
(QB_NEW_FR)
[typographical] ~70-~70: Caractère d’apostrophe incorrect.
Context: ...플러그인 관계 repomix-mcp 플러그인을 기반으로 권장합니다. repomix-commands 플러그인은 편리한 슬래시 명령을 제공하고...
(APOS_INCORRECT)
[typographical] ~70-~70: Caractère d’apostrophe incorrect.
Context: ...pomix-commands플러그인은 편리한 슬래시 명령을 제공하고,repository-explorer`는 AI 기반 분석 기능을 추가합니다. 독립적으로 설치할 수 있지만, 세...
(APOS_INCORRECT)
[grammar] ~113-~113: Il y a peut-être une erreur ici
Context: ...포함" - "특정 디렉토리 패키징" ### AI로 로컬 코드베이스 탐색 AI 기반 분석을 위해 `/repository-explorer:explo...
(QB_NEW_FR)
[typographical] ~115-~115: Une espace est requise.
Context: ...패키징" ### AI로 로컬 코드베이스 탐색 AI 기반 분석을 위해 /repository-explorer:explore-local 명령을 사용합니다: ```text /repo...
(DEUX_POINTS_ESPACE)
[grammar] ~115-~115: Typographie
Context: .../repository-explorer:explore-local` 명령을 사용합니다: text /repository-explorer:explore-local ./src 인증 관련 코드를 모두 찾아줘 기타 예제: - "이 프로젝트의 구조를 분석해줘" - "주요 컴포넌트를 ...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~122-~122: Typographie
Context: ...re-local ./src 인증 관련 코드를 모두 찾아줘 ``` 기타 예제: - "이 프로젝트의 구조를 분석해줘" - "주요 컴포넌트를 보여줘" -...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~123-~123: Élément manquant
Context: ...련 코드를 모두 찾아줘 ``` 기타 예제: - "이 프로젝트의 구조를 분석해줘" - "주요 컴포넌트를 보여줘" - "모든 API 엔드포인트를 찾아줘" ...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~124-~124: Élément manquant
Context: ...기타 예제: - "이 프로젝트의 구조를 분석해줘" - "주요 컴포넌트를 보여줘" - "모든 API 엔드포인트를 찾아줘" ### AI로 원격 저장소 탐...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~125-~125: Élément manquant
Context: ...분석해줘" - "주요 컴포넌트를 보여줘" - "모든 API 엔드포인트를 찾아줘" ### AI로 원격 저장소 탐색 GitHub 저장소를 분석하려면 `/repos...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~127-~127: Il y a peut-être une erreur ici
Context: ...- "모든 API 엔드포인트를 찾아줘" ### AI로 원격 저장소 탐색 GitHub 저장소를 분석하려면 `/repository-explorer:...
(QB_NEW_FR)
[typographical] ~129-~129: Une espace est requise.
Context: ..." ### AI로 원격 저장소 탐색 GitHub 저장소를 분석하려면 /repository-explorer:explore-remote 명령을 사용합니다: ```text /rep...
(DEUX_POINTS_ESPACE)
[grammar] ~129-~129: Typographie
Context: ...repository-explorer:explore-remote` 명령을 사용합니다: text /repository-explorer:explore-remote facebook/react 주요 컴포넌트 아키텍처를 보여줘 기타 예제: - "저장소의 모든 React 훅을 찾아줘" - "프로젝트 ...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~136-~136: Typographie
Context: ...acebook/react 주요 컴포넌트 아키텍처를 보여줘 ``` 기타 예제: - "저장소의 모든 React 훅을 찾아줘" - "프로젝트 구조를 설명...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~137-~137: Élément manquant
Context: ...텍처를 보여줘 ``` 기타 예제: - "저장소의 모든 React 훅을 찾아줘" - "프로젝트 구조를 설명해줘" - "에러 바운더리는 어디에 정의되어 ...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~138-~138: Élément manquant
Context: ...제: - "저장소의 모든 React 훅을 찾아줘" - "프로젝트 구조를 설명해줘" - "에러 바운더리는 어디에 정의되어 있어?" ## 관련 리소스 -...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~139-~139: Il y a peut-être une erreur ici
Context: ...프로젝트 구조를 설명해줘" - "에러 바운더리는 어디에 정의되어 있어?" ## 관련 리소스 - MCP 서버 문서...
(QB_NEW_FR)
[grammar] ~155-~155: Il y a peut-être une erreur ici
Context: ...lugins/repomix-commands) - 저장소 탐색기 플러그인 ## 피드백 및 지원 Claude Code 플러그인에 대한 문제가 발생하거나...
(QB_NEW_FR)
.claude/plugins/repository-explorer/agents/repository-explorer.md
[grammar] ~34-~34: Use a hyphen to join words.
Context: ...nd all database models" - "Show me error handling code" ### Metrics and Statisti...
(QB_NEW_EN_HYPHEN)
[style] ~160-~160: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...utput files** after analysis if they're very large ### Output Format - XML (default):...
(EN_WEAK_ADJECTIVE)
[style] ~301-~301: Consider using a more formal alternative.
Context: ... ## Help and Documentation If you need more information: - Run npx repomix@latest --help to s...
(MORE_INFO)
[style] ~326-~326: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...up or mention cleanup if output file is very large? Remember: Your goal is to make reposi...
(EN_WEAK_ADJECTIVE)
.claude/plugins/repository-explorer/commands/explore-remote.md
[style] ~7-~7: Consider using an alternative to strengthen your wording.
Context: ... When the user runs this command, they want to explore and understand a remote repo...
(WANT_KEEN)
🪛 markdownlint-cli2 (0.18.1)
.claude/plugins/repository-explorer/commands/explore-local.md
27-27: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
42-42: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
.claude/plugins/repomix-commands/commands/pack-local.md
87-87: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
.claude/plugins/repository-explorer/agents/repository-explorer.md
27-27: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
42-42: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
- GitHub Check: Build and run (windows-latest, 24.x)
- GitHub Check: Build and run (windows-latest, 20.x)
- GitHub Check: Build and run (ubuntu-latest, 20.x)
- GitHub Check: Build and run (windows-latest, 22.x)
- GitHub Check: Build and run with Bun (windows-latest, latest)
- GitHub Check: Test (windows-latest, 20.x)
- GitHub Check: Test (windows-latest, 24.x)
- GitHub Check: Test (windows-latest, 22.x)
- GitHub Check: Test with Bun (windows-latest, latest)
- GitHub Check: claude-review
- GitHub Check: Cloudflare Pages
🔇 Additional comments (44)
.claude/plugins/repomix-commands/commands/pack-remote.md (1)
106-106: Clear and well-positioned reinforcement of sub-agent delegation.The updated reminder succinctly encapsulates the new guidance: execute repomix commands, then delegate analysis to sub-agents. This mirrors the teaching in the earlier "Analyzing the Output" section and helps users develop the right mental model.
website/client/src/pt-br/guide/claude-code-plugins.md (6)
25-43: Comprehensive and well-structured new plugin section.The repository-explorer plugin documentation is well-organized with clear features, available commands, and workflow explanation. The content flows naturally and maintains consistency with the existing plugin sections.
64-66: Installation command added correctly.The new installation instruction for repository-explorer is properly formatted and follows the existing pattern for plugin installation commands.
69-71: Updated plugin relationship description is clear and comprehensive.The relationship explanation now properly describes how all three plugins (repomix-mcp, repomix-commands, and repository-explorer) integrate and complement each other, providing users with clear guidance on installation choices.
113-140: Usage examples for repository-explorer are well-presented.Both the local exploration and remote GitHub repository exploration examples are clearly structured, with practical command examples and additional use-case suggestions that mirror the format of existing examples. The examples effectively demonstrate the natural-language capabilities of the plugin.
148-155: Plugin source code reference added appropriately.The new link to the repository-explorer plugin source code is correctly formatted and placed alongside the existing plugin source links, maintaining consistency and discoverability.
69-70: Minor: Address static analysis punctuation flag.The static analysis tool flagged a potential double punctuation at line 69, though this appears to be a false positive (normal markdown transition between code block and admonition). However, you may want to verify the markdown rendering to ensure the spacing and formatting display correctly across all platforms.
website/client/src/zh-cn/guide/claude-code-plugins.md (4)
25-43: Plugin documentation is comprehensive and accurate.The repository-explorer plugin section correctly describes the AI-powered analysis capabilities, lists all available commands, and explains the workflow. Content aligns well with the PR objectives and follows the established documentation pattern.
65-71: Installation guidance and plugin relationship description are clear.The new installation instruction for repository-explorer is properly formatted, and the plugin relationship tip accurately describes how all three plugins work together while remaining optionally independent.
113-140: Usage examples for AI-assisted exploration are practical and well-structured.Both local and remote repository exploration examples follow the existing pattern, provide realistic use cases, and clearly demonstrate command usage and natural-language prompts.
155-155: Plugin source reference correctly added.The GitHub link for the repository-explorer plugin source code is properly formatted and consistent with the links for other plugins.
website/client/src/ja/guide/claude-code-plugins.md (5)
25-43: Repository-explorer plugin section is well-structured and comprehensive.The new plugin documentation follows the established pattern of the existing plugins. It clearly describes the plugin's purpose, features, available commands, and workflow. The three-step "how it works" explanation (pack repo → use grep/read tools → provide analysis) aligns with the plugin's design intent from the PR objectives.
65-66: Installation and plugin relationship guidance appropriately updated.The installation command for repository-explorer follows the same format as existing plugins. The updated plugin relationship note (line 70) correctly references all three plugins and recommends using them together, which provides good guidance to users.
Also applies to: 70-70
113-140: Usage examples for AI-driven exploration are clear and practical.The examples for both
/repository-explorer:explore-localand/repository-explorer:explore-remotedemonstrate realistic task scenarios and variations. The natural-language instructions align with the plugin's intended use case of intelligent, conversational codebase analysis.
155-155: Source code link added consistently.The repository-explorer plugin source link follows the same format and structure as the links for repomix-mcp and repomix-commands plugins.
1-156: Verify translation consistency with English source and other language versions.Since this is a localized Japanese guide, ensure the translation is consistent with the English source version and other language translations being added (11 additional languages per PR objectives). The technical terminology, command names, and feature descriptions should align across all language versions.
This verification can be done by comparing this file with the English version (
website/client/src/en/guide/claude-code-plugins.mdor similar) and spot-checking 1-2 other language versions to ensure consistent structure and terminology.website/client/src/zh-tw/guide/claude-code-plugins.md (5)
25-43: New repository-explorer plugin section is well-structured and consistent.The addition of the repository-explorer plugin documentation (lines 25–43) mirrors the format and depth of the existing repomix-mcp and repomix-commands sections. The features are clearly articulated in Traditional Chinese, command names are preserved, and the "How it works" explanation provides helpful context.
65-66: Plugin installation command is consistent with existing patterns.The new installation command for repository-explorer follows the same format as the MCP and commands plugins, ensuring clarity and ease of discovery.
70-70: Plugin relationship explanation correctly expanded to three plugins.The updated relationship note now references all three plugins (repomix-mcp, repomix-commands, repository-explorer) and articulates their complementary roles, helping users understand the combined workflow.
113-140: Usage examples for repository-explorer are clear and actionable.Both local and remote exploration examples follow the same structure as existing pack-local and pack-remote examples, with sample prompts that demonstrate typical use cases. The examples are concrete and linguistically natural for Traditional Chinese users.
Verify that the command examples (e.g.,
/repository-explorer:explore-local ./src,/repository-explorer:explore-remote facebook/react) match the actual agent implementation and available command signatures.
155-155: Resource link for repository-explorer plugin source is added.The new plugin source link follows the established pattern and maintains consistency with the existing MCP and commands plugin references.
website/client/src/de/guide/claude-code-plugins.md (5)
25-43: Content is well-integrated and accurate.The new repository-explorer plugin section follows the established pattern and provides clear descriptions of features, commands, and workflow. The German terminology is appropriate and consistent with the document.
65-66: Installation command is clear and consistent.The added repository-explorer installation line follows the established pattern and includes a helpful clarifying comment.
69-71: Plugin relationship description is clear and helpful.The updated tip box accurately explains how all three plugins complement each other and provides useful guidance for users on which combinations to install.
113-140: Usage examples follow established patterns and are clear.The new AI-powered exploration examples are well-structured, concrete, and consistent with the existing repomix-commands examples. The example scenarios effectively demonstrate the plugin's local and remote capabilities.
148-155: Source code links are complete and properly formatted.The new repository-explorer plugin link is added consistently alongside the existing plugin links in the "Plugin-Quellcode" section.
website/client/src/vi/guide/claude-code-plugins.md (5)
25-43: Documentation of new plugin introduction looks solid.The new repository-explorer plugin section is well-structured, accurately describes the plugin's capabilities per the PR objectives, and the addition of a "Cách hoạt động" (How it works) workflow is helpful documentation. The section integrates cleanly with the existing plugin documentation.
65-66: Installation instructions follow established pattern.The new installation command is consistent with the existing plugin installation syntax and clearly documented with a comment.
69-71: Plugin relationship note clearly explains the three-plugin ecosystem.The updated tip box accurately conveys the intended relationship between the three plugins, explaining that while independent use is supported, combined use provides the fullest experience.
113-140: Usage examples are practical and well-structured.The new examples for local and remote exploration using repository-explorer effectively demonstrate the plugin's capabilities with realistic, natural-language prompts that follow the established documentation pattern.
155-155: Source code reference correctly added.The new plugin source reference is correctly positioned in the "Mã Nguồn Plugin" section and follows the established URL pattern.
website/client/src/fr/guide/claude-code-plugins.md (2)
65-70: Installation and plugin relationships section looks good.The new repository-explorer installation command follows the established pattern, and the updated plugin relationships description clearly explains how the three plugins complement each other.
148-155: Source code link section looks good.The new repository-explorer plugin link is properly formatted and consistent with existing plugin documentation.
.claude/plugins/repomix-commands/.claude-plugin/plugin.json (1)
4-4: Version bump is appropriate and consistent with marketplace updates.This aligns with the addition of new sub-agent guidance in pack-local.md and the broader plugin ecosystem expansion.
.claude/plugins/repomix-commands/commands/pack-local.md (1)
65-99: Excellent addition: sub-agent delegation guidance improves user workflow.The new "Analyzing the Output" section properly directs users to repository-explorer or similar agents, preventing excessive context consumption. The workflow example and agent selection strategy are clear and actionable. This integrates well with the new repository-explorer plugin introduced in this PR.
.claude/plugins/repository-explorer/.claude-plugin/plugin.json (1)
1-10: Plugin manifest is well-formed and metadata is complete.The repository-explorer plugin definition properly describes the AI-powered analysis agent with appropriate keywords and accurate description. Version 1.0.0 is suitable for the initial release.
.claude/plugins/repository-explorer/agents/repository-explorer.md (1)
1-50: Comprehensive and well-structured agent definition with clear workflows.The agent documentation provides thorough instructions for repository exploration via Repomix CLI, including detailed workflows, tool usage patterns, best practices, and example scenarios. The responsibilities section clearly articulates the agent's role, and the integration with Bash, Grep, and Read tools is well-documented.
.claude/plugins/repository-explorer/commands/explore-local.md (1)
1-72: Clear command documentation with practical usage guidance.The explore-local command documentation properly explains the workflow, provides appropriate examples, and includes a clear task template for delegating to the repository-explorer agent. The command flow section effectively guides implementers on how to invoke the agent with proper context.
.claude-plugin/marketplace.json (1)
8-8: Marketplace configuration looks good.The JSON is well-formed, the new
repository-explorerplugin entry is complete with all required fields, and it follows the established pattern. Version bumps (metadata andrepomix-commandsto 1.0.2, new plugin at 1.0.0) are sensible for a coordinated release with a new addition.Also applies to: 28-28, 37-49
website/client/src/id/guide/claude-code-plugins.md (1)
25-43: Indonesian localization is complete and consistent.The additions for
repository-exploreracross installation, plugin relationships, usage examples, and source links are well-integrated into the localized guide. Structure and command syntax align with the English version.Also applies to: 65-66, 70-70, 113-140, 155-155
website/client/src/es/guide/claude-code-plugins.md (1)
25-43: Spanish localization is structurally complete and consistent.The additions for
repository-explorerare fully integrated across the guide. Command syntax and three-plugin narrative align with the English reference version.Note: Static analysis tools flagged several optional Spanish language style suggestions (anglicisms, punctuation conventions, word choice). These are non-critical and can be addressed if stricter Spanish language guidelines are preferred, but they do not impede understanding or functionality.
Also applies to: 65-66, 70-70, 113-140, 155-155
website/client/src/en/guide/claude-code-plugins.md (3)
25-43: Repository-explorer plugin section is clear and comprehensive.The feature list, available commands, and workflow description are well-articulated and align with the PR objectives. The three-tier plugin narrative (base MCP → slash commands → AI analysis) effectively positions this new plugin in the ecosystem.
69-71: Plugin relationship explanation is effective.The note clearly communicates that while plugins can be installed independently, using all three provides the most complete experience. This guidance helps users understand the intended integration layer.
113-140: Usage examples are concrete and realistic.The examples for both local and remote exploration clearly demonstrate how users would invoke the AI-powered exploration workflow. The progression from command invocation to specific queries is helpful.
Update all grep command examples in repository-explorer agent to use the -E flag when using pipe (|) for pattern alternation. Without -E, grep searches for literal pipe characters instead of performing regex alternation. Changes: - Line 137: grep -i → grep -iE for export patterns - Line 140: grep -i → grep -iE for authentication patterns - Lines 174-192: All search pattern examples updated to use grep -iE - Line 231: Example 2 workflow updated to use grep -iE - Line 247: Example 3 workflow updated to use grep -iE This addresses the code review feedback from Copilot on PR #908.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
.claude/plugins/repository-explorer/agents/repository-explorer.md
Outdated
Show resolved
Hide resolved
Pull Request Review: repository-explorer PluginGreat work on adding a comprehensive AI-powered repository analysis plugin! This is a well-structured addition that follows the existing plugin patterns. StrengthsPlugin Architecture & Design:
Documentation Quality:
Issues Found1. Communication Style (CRITICAL - see inline comment)
2. File Cleanup Strategy
3. Missing Error Handling
4. Security Considerations
5. Performance Optimization
6. Version Numbering
Premortem: Potential Failure Scenarios
RecommendationsHigh Priority (Fix Before Merge):
Medium Priority: Low Priority (Future): Final ThoughtsThis is a well-designed and valuable addition. After addressing the critical language issue, this should be ready to merge. Other recommendations can be follow-up PRs. Estimated effort to fix critical issues: 15-30 minutes Great work overall! |
… analysis Add new Claude Code plugin that provides an intelligent repository analysis agent using Repomix CLI. This plugin enables users to explore and analyze both local and remote repositories through natural language interactions. Features: - AI agent that runs repomix commands and analyzes output files - Slash commands: /explore-remote and /explore-local - Incremental exploration using grep and read operations - Support for pattern discovery, structure analysis, and metrics - Automatic security checks and compression for large repos The agent intelligently translates user requests into repomix commands, then uses Grep and Read tools to efficiently search and analyze the generated output files without reading entire contents. Updated marketplace.json version to 1.0.2 to include the new plugin.
…xt overflow Add comprehensive guidance for handling large repomix output files by delegating analysis to appropriate sub-agents instead of reading files directly. Changes to repomix-commands plugin: - Add "Analyzing the Output" section to pack-local.md and pack-remote.md - Provide agent selection strategy with fallback options - Emphasize using repository-explorer agent if available, otherwise general-purpose or other suitable sub-agents - Include concrete examples of workflow with sub-agent delegation Changes to repository-explorer plugin: - Enhance explore-local.md and explore-remote.md with detailed task templates - Add note that repository-explorer agent is guaranteed to be available - Provide structured instruction templates for agent tasks - Clarify the optimized workflow and incremental analysis approach These changes prevent excessive context consumption by ensuring large output files are analyzed incrementally through sub-agents using Grep and Read tools rather than being loaded entirely into context.
…xt overflow Add comprehensive guidance for handling large repomix output files by delegating analysis to appropriate sub-agents instead of reading files directly. Changes to repomix-commands plugin: - Add "Analyzing the Output" section to pack-local.md and pack-remote.md - Provide agent selection strategy with fallback options - Emphasize using repository-explorer agent if available, otherwise general-purpose or other suitable sub-agents - Include concrete examples of workflow with sub-agent delegation Changes to repository-explorer plugin: - Enhance explore-local.md and explore-remote.md with detailed task templates - Add note that repository-explorer agent is guaranteed to be available - Provide structured instruction templates for agent tasks - Clarify the optimized workflow and incremental analysis approach These changes prevent excessive context consumption by ensuring large output files are analyzed incrementally through sub-agents using Grep and Read tools rather than being loaded entirely into context.
Add comprehensive documentation for the new repository-explorer plugin across README and website documentation (English and Japanese versions). Changes: - README.md: Add repository-explorer as the 3rd plugin with features, commands, and usage examples - Update installation section with repository-explorer install command - Update plugin relationship note to mention all three plugins Website documentation (en/ja): - Add repository-explorer plugin section with features and commands - Add AI-powered analysis usage examples for local and remote exploration - Update installation instructions and plugin relationship tips - Add repository-explorer to plugin source code links Other changes: - Bump marketplace.json version to 1.0.2 - Bump repomix-commands plugin version to 1.0.2 The repository-explorer plugin provides AI-powered codebase analysis that intelligently explores repositories using natural language commands while managing context efficiently through incremental grep and read operations.
…tations Add comprehensive documentation for the repository-explorer plugin across all language versions of the website documentation. Updated languages: - de (German) - es (Spanish) - fr (French) - hi (Hindi) - id (Indonesian) - ko (Korean) - pt-br (Portuguese Brazilian) - vi (Vietnamese) - zh-cn (Chinese Simplified) - zh-tw (Chinese Traditional) Changes for each language: - Add repository-explorer as 3rd plugin section with features and commands - Add AI-powered analysis usage examples (local and remote exploration) - Update installation instructions with repository-explorer install command - Update plugin relationship tips to mention all three plugins - Add repository-explorer to plugin source code links All translations follow the pattern established in English (en) and Japanese (ja) versions, with natural language adaptations appropriate for each locale.
Update all grep command examples in repository-explorer agent to use the -E flag when using pipe (|) for pattern alternation. Without -E, grep searches for literal pipe characters instead of performing regex alternation. Changes: - Line 137: grep -i → grep -iE for export patterns - Line 140: grep -i → grep -iE for authentication patterns - Lines 174-192: All search pattern examples updated to use grep -iE - Line 231: Example 2 workflow updated to use grep -iE - Line 247: Example 3 workflow updated to use grep -iE This addresses the code review feedback from Copilot on PR #908.
…CodeRabbit Remove language-specific directive and improve markdown code blocks based on automated code review feedback. Changes: - Remove "Communicate in Japanese" instruction from repository-explorer agent This directive was inconsistent with multilingual documentation and unnecessarily constrained agent responses (Copilot/Gemini feedback) - Add language identifier to code blocks in pack-local.md and pack-remote.md Changed ``` to ```text for proper syntax highlighting and markdown linting compliance (CodeRabbit feedback) These changes improve the plugin's internationalization support and markdown quality without affecting functionality.
yamadashy
force-pushed
the
feat/repomix-explore-agent-plugin
branch
from
4bf2317 to
cc47b3f
Compare
PR Review: feat(plugins): Add repository-explorer pluginOverviewThis PR introduces a well-designed AI-powered repository analysis plugin that leverages Repomix CLI for intelligent codebase exploration. The implementation follows the existing plugin patterns and provides comprehensive documentation. ✅ Strengths
🔍 Code Quality ReviewAgent Definition (.claude/plugins/repository-explorer/agents/repository-explorer.md:1-325)Strengths:
Minor Issues:
Command Files Reviewexplore-local.md & explore-remote.md:
Suggestion: Consider adding validation examples for handling invalid paths or repository URLs Integration Updatesrepomix-commands updates:
marketplace.json:
|
PR Review: repository-explorer PluginThanks for this comprehensive addition! This is a well-structured plugin that adds significant value to the Repomix ecosystem. Here is my detailed review: StrengthsExcellent Documentation
Well-Designed Architecture
Strong Integration
Code Quality and Best PracticesPlugin Structure
Agent Definition Quality
Command Files
Documentation
Potential Issues and Concerns1. Minor: Missing Space in Example (Line 2)There is a missing space between two examples in the frontmatter. Add proper spacing between examples for better readability. 2. Documentation ConsistencyThe version bumps are inconsistent:
Question: Should repository-explorer start at 1.0.0 or align with the marketplace version (1.0.2)? Premortem Analysis: Potential Failure ScenariosI have performed a premortem analysis to identify potential issues before deployment: Edge Cases and Integration Issues1. Large Repository Handling
2. Output File Collision
3. Network Failures for Remote Repos
4. Path Resolution Issues
5. Context Window Exhaustion
User Experience Issues6. Long Running Operations
Security Concerns7. Sensitive Repository Analysis
Recommendations for Future EnhancementsShort-term (Consider for this PR)
Medium-term (Future PRs)
Test Coverage AssessmentManual Testing Checklist (per PR description):
Recommended Additional Testing:
Note: Since this is primarily configuration/documentation, automated unit tests may not be necessary. SummaryThis is an excellent addition to the Repomix plugin ecosystem! The implementation is thorough, well-documented, and follows best practices. The identified issues are minor and do not block the PR. Verdict: Approve with minor suggestionsThe premortem analysis reveals mostly edge cases that are adequately addressed by the current design. The suggested improvements are primarily for polish and can be addressed now or in follow-up PRs. Confidence Level: High - This plugin is production-ready with minor fixes. Action ItemsMust address before merge:
Nice to have (can defer):
Great work! |
…tmatter Add newline between example blocks in YAML frontmatter for better readability and consistency with markdown formatting standards. This is a minor formatting improvement that doesn't affect functionality.
Summary
Add a new Claude Code plugin
repository-explorerthat provides AI-powered repository analysis capabilities using Repomix CLI.Changes
New Plugin: repository-explorer
Plugin Components
Agent Definition (
.claude/plugins/repository-explorer/agents/repository-explorer.md)Slash Commands
/repository-explorer:explore-local- Analyze local codebases with AI assistance/repository-explorer:explore-remote- Analyze remote GitHub repositories with AI assistanceDocumentation Updates
Related Plugin Updates
Other Changes
How It Works
npx repomix@latestto pack the repositoryBenefits
Testing
Checklist
npm run testnpm run lint