Skip to content

feat(skills): Add repomix-explorer agent skill#1103

Merged
yamadashy merged 5 commits intomainfrom
feat/add-repomix-explorer-skill
Jan 17, 2026
Merged

feat(skills): Add repomix-explorer agent skill#1103
yamadashy merged 5 commits intomainfrom
feat/add-repomix-explorer-skill

Conversation

@yamadashy
Copy link
Copy Markdown
Owner

Add a new Claude Code skill for analyzing and exploring codebases using Repomix CLI.

Changes

  • Add .claude/skills/repomix-explorer/SKILL.md - comprehensive guide for AI agents to analyze repositories
  • Supports both remote (GitHub) and local repository analysis
  • Includes workflow instructions, common options, search patterns, and best practices
  • Remote repository output goes to /tmp to avoid polluting user's project directory

Key Features

  • Remote repository analysis with --remote flag
  • Local directory analysis
  • Pattern discovery (auth, API, models, etc.)
  • Support for --compress on large repos
  • Support for --remote-branch to specify branch/tag/commit

Checklist

  • Run npm run test (N/A - Markdown file only)
  • Run npm run lint (N/A - Markdown file only)

Add a new skill for analyzing and exploring codebases using Repomix CLI.
This skill is independent from the existing plugin implementation.
Updated repomix-explorer skill to always output to /tmp for remote
repository analysis. This prevents polluting the user's current
project directory with analysis output files.
- Remove incorrect .txt reference (default is .xml only)
- Add --remote-branch option for specifying branch/tag/commit
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 17, 2026

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit 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.

📝 Walkthrough

Walkthrough

A new Markdown skill guide for repomix-explorer is introduced, documenting its capabilities for repository analysis, user intents, workflow steps, available tools (Bash, Grep, Read), best practices, and example workflows for constructing and executing repomix commands.

Changes

Cohort / File(s) Summary
Repomix-explorer Skill Guide
.claude/skills/repomix-explorer/SKILL.md
New skill documentation defining repomix-explorer intent (remote/local repository analysis, pattern discovery, metrics), workflow steps, available tools, best practices, example workflows, error handling procedures, and security considerations for executing repomix commands and generating insights.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding a new repomix-explorer skill to the Claude Code agent system.
Description check ✅ Passed The description covers key aspects (changes, features, checklist) and addresses the template requirements with appropriate context for a Markdown-only contribution.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/add-repomix-explorer-skill

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @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 integrates a new AI agent skill, repomix-explorer, to enhance the agent's capability in understanding and navigating codebases. The skill provides a structured approach for AI agents to leverage the Repomix CLI, enabling them to efficiently analyze repository structures, identify code patterns, and report key insights from both remote and local projects. This addition aims to streamline the process of code exploration and analysis for AI-driven tasks.

Highlights

  • New Agent Skill Added: Introduced a new Claude Code skill named repomix-explorer specifically designed for analyzing and exploring codebases using the Repomix CLI.
  • Comprehensive Guidance for AI Agents: The new skill includes a detailed SKILL.md guide that outlines user intent examples, agent responsibilities, available tools (Bash, Grep, Read), a step-by-step workflow for repository analysis, best practices, common search patterns, and error handling.
  • Support for Remote and Local Repositories: The repomix-explorer skill enables analysis of both remote GitHub repositories and local project directories, offering flexibility in codebase examination.
  • Output Management and Efficiency: Remote repository analysis outputs are directed to the /tmp directory to prevent polluting the user's project, and the skill emphasizes using --compress for large repositories to optimize token usage and efficiency.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Jan 17, 2026

Deploying repomix with  Cloudflare Pages  Cloudflare Pages

Latest commit: f636b8c
Status: ✅  Deploy successful!
Preview URL: https://30c36ae5.repomix.pages.dev
Branch Preview URL: https://feat-add-repomix-explorer-sk.repomix.pages.dev

View logs

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Jan 17, 2026

Code Review: feat(skills): Add repomix-explorer agent skill

Reviewer: Claude (AI)

Summary

This PR adds a new Claude Code skill (repomix-explorer) for analyzing and exploring codebases using the Repomix CLI. The skill provides comprehensive guidance for AI agents to work with both remote and local repositories.

Overall Assessment: Approve with Minor Suggestions

The implementation is well-documented and follows the established skill file conventions in this repository. The content is thorough and provides actionable guidance for AI agents.

Detailed Feedback

Strengths

  1. Comprehensive Documentation: The skill covers a wide range of use cases including remote/local analysis, pattern discovery, and metrics collection.

  2. Good Best Practices: Properly emphasizes:

    • Using /tmp for remote repo output to avoid polluting user directories
    • Compression for large repos (>100k lines)
    • Grep-first approach before reading large files
  3. Practical Examples: Includes 5 concrete workflow examples that cover common scenarios.

  4. Consistent with Existing Skills: The format follows the established pattern seen in other skills like lint-fixer, agent-memory, and website-maintainer.

  5. Good Addition of --remote-branch: The third commit correctly added this useful option.

Suggestions for Improvement

1. Potential Duplication with Plugin

The repository already has a similar explorer agent at .claude/plugins/repomix-explorer/agents/explorer.md. The PR description mentions this is "independent from the existing plugin implementation," but it might be helpful to:

  • Add a note in the skill about when to use the skill vs the plugin
  • Or consider deprecating one approach to avoid confusion

2. Minor Inconsistencies

  • Line 192: The File Management section mentions default output as ./repomix-output.xml but the skill also instructs to use /tmp for remote repos. Consider adding a note that this default applies only to local analysis.

  • Self-Verification Checklist (lines 311-322): The existing plugin version uses checkmarks (✓) in the checklist items, but this skill version uses plain dashes. Minor inconsistency in style.

3. Missing Option

Consider documenting the --top-files-len option which can be useful for understanding which files contribute most to token count.

Premortem Analysis: Potential Failure Scenarios

Risk Assessment
Risk Likelihood Impact Mitigation
Output file path conflicts when analyzing multiple repos Medium Low Document using unique output paths (already covered)
/tmp directory permissions on some systems Low Medium Consider fallback directory suggestion
Large repos timing out with npx Medium Medium Already recommends --compress; could add timeout guidance
Confusion between skill and plugin Medium Low Document the relationship between the two

Deployment Risk: Low - This is a documentation-only change (Markdown file) with no code impact.

Verdict

Approve - This is a valuable addition that provides comprehensive guidance for AI agents to explore codebases. The minor suggestions above are optional improvements and don't block merging.


Review generated by Claude

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new repomix-explorer skill for a Claude agent, providing a comprehensive guide for analyzing codebases. The documentation is well-structured, but it contains a critical inconsistency regarding the tools the agent should use. It introduces a Grep Tool and Read Tool as preferred, but then instructs the agent to only use the Bash tool and provides only bash examples. This contradiction could confuse the agent. I've provided a suggestion to align the documentation. Additionally, I've identified a few issues in the grep patterns provided, including one that would cause a command to fail, and have suggested corrections for clarity and correctness.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.claude/skills/repomix-explorer/SKILL.md:
- Line 207: The markdown file contains several fenced code blocks with no
language hint (plain ```), causing MD040; update each empty fenced block in
SKILL.md to include a language identifier by replacing ``` with ```text for the
occurrences noted (the blocks at the current location and the other examples
referenced), and apply the same `text` tag to the other example blocks so all
fences include a language hint.
🧹 Nitpick comments (1)
.claude/skills/repomix-explorer/SKILL.md (1)

15-15: Replace bare URLs with proper Markdown links.

Markdownlint flags bare URLs; wrap them in link syntax to satisfy MD034.

🛠️ Suggested fix
-- "What's the structure of facebook/react?"
+- "What's the structure of [facebook/react](https://github.com/facebook/react)?"

...
-- Check the official documentation at https://github.com/yamadashy/repomix
+- Check the official documentation at [github.com/yamadashy/repomix](https://github.com/yamadashy/repomix)

Also applies to: 299-299

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.17%. Comparing base (621a066) to head (f636b8c).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1103   +/-   ##
=======================================
  Coverage   87.17%   87.17%           
=======================================
  Files         116      116           
  Lines        4382     4382           
  Branches     1019     1019           
=======================================
  Hits         3820     3820           
  Misses        562      562           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Escape backslash properly to avoid shell error with grep -E.
- Add 'text' language identifier to example code blocks (MD040)
- Remove redundant 'Error' from case-insensitive grep pattern
@claude
Copy link
Copy Markdown
Contributor

claude bot commented Jan 17, 2026

Code Review: feat(skills): Add repomix-explorer agent skill

Reviewer: Claude (AI)

Summary

This PR adds a new Claude Code skill (repomix-explorer) for analyzing and exploring codebases using the Repomix CLI. The skill provides comprehensive guidance for AI agents to work with both remote and local repositories.

Overall Assessment: ✅ Approve

The implementation is well-structured and provides valuable documentation. I have a few observations for consideration.


Key Observations

1. Relationship with Existing Plugin

The repository already has a similar implementation at .claude/plugins/repomix-explorer/agents/explorer.md. The PR description mentions this is "independent from the existing plugin implementation."

Differences between skill and plugin versions:

  • Skill version (this PR):

    • Outputs remote repos to /tmp (good practice)
    • Includes --remote-branch option
    • Fixed escape for require\\( pattern (correct)
    • Uses plain dashes in self-verification checklist
    • Removes .txt reference from File Management section
  • Plugin version (existing):

    • No /tmp output directive for remote repos
    • Missing --remote-branch option
    • Has incorrect escape require\( (would fail in some contexts)
    • Uses checkmarks (✓) in self-verification checklist
    • References ./repomix-output.xml or ./repomix-output.txt

Suggestion: Consider backporting the improvements (especially the /tmp output and --remote-branch option) to the plugin version for consistency, or add a note about which approach to prefer.

2. Code Block Language Hints (Minor)

CodeRabbit flagged that some code blocks (lines 207, 222, 237, 249, 261) use plain ``` without a language identifier. While this is technically a markdownlint issue (MD040), it's minor for a skill documentation file where the content is workflow descriptions rather than executable code.

Priority: Not needed - These blocks describe workflows, not executable code, so a language hint isn't strictly necessary.

3. Bare URLs (Minor)

Line 299 has a bare URL: https://github.com/yamadashy/repomix. Converting to a Markdown link would satisfy MD034.

Priority: Not needed - This is a minor style issue that doesn't affect functionality.


Strengths

  1. Thoughtful output management - Using /tmp for remote repos prevents polluting user directories
  2. Comprehensive coverage - Covers remote/local analysis, pattern discovery, metrics, and error handling
  3. Fixed grep escape - The require\\( pattern is correctly escaped for shell usage
  4. Added --remote-branch - Useful option for specifying branches/tags/commits
  5. Good best practices - Emphasizes compression for large repos and grep-first approach

Premortem Analysis

Risk Likelihood Impact Mitigation
Confusion between skill vs plugin Medium Low Consider documentation clarifying when to use each
/tmp directory permissions vary Low Low Standard location, widely accessible
Large repos timing out Medium Medium Already recommends --compress

Deployment Risk: Very Low - This is a documentation-only change (Markdown file) with no code impact.


Verdict

Approve - This is a valuable addition that provides clear, actionable guidance for AI agents exploring codebases. The minor markdown style suggestions from other bots are optional and don't block merging.


Review generated by Claude

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Jan 17, 2026

Code Review Update: feat(skills): Add repomix-explorer agent skill

Reviewer: Claude (AI) - Updated Review

Summary

I've re-reviewed this PR after examining all existing feedback and comparing with the existing plugin implementation. This is a documentation-only change adding a new skill file.

Overall Assessment: ✅ Approve

The skill is well-documented and includes several improvements over the existing plugin version.


Key Improvements in This Skill vs Existing Plugin

Aspect New Skill (.claude/skills/) Existing Plugin (.claude/plugins/)
Remote output path Uses /tmp (good practice) No explicit /tmp directive
--remote-branch option ✅ Documented ❌ Missing
require() grep pattern require\\\\( (correct) require\( (may fail)
File management Removed .txt reference References .xml or .txt

AI Bot Comment Evaluation

Gemini Code Assist Feedback

Gemini mentioned a "critical inconsistency" about tools - stating the skill introduces Grep/Read tools but only provides bash examples.

Priority: Not needed

This is a false positive. The skill correctly documents all three tools (Bash, Grep, Read) in the "Available Tools" section (lines 51-72), explains their preferred usage, and the bash grep examples in the patterns section are appropriate since they show the pattern syntax that works with both bash grep and the Grep tool. The agent is expected to use the Grep Tool for actual searches while the patterns shown are portable.

CodeRabbit Feedback

1. Bare URLs (MD034) - Lines 15, 299:
Priority: Not needed

The line 15 example ("What's the structure of facebook/react?") is a user intent example showing how users might phrase questions - converting to a markdown link would make it look unnatural. Line 299 is documentation reference - acceptable as-is.

2. Fenced code blocks without language hint (MD040) - Lines 207, 222, etc.:
Priority: Not needed

These blocks contain workflow descriptions, not executable code. Using text was already applied in the latest commit (f636b8c), so this was already addressed.


Remaining Observations

Skill vs Plugin Relationship

The repository now has two similar implementations:

  • Skill: .claude/skills/repomix-explorer/SKILL.md (this PR)
  • Plugin: .claude/plugins/repomix-explorer/agents/explorer.md (existing)

The PR description notes this is "independent from the existing plugin implementation." The skill version has improvements (especially /tmp output and --remote-branch).

Suggestion for future: Consider backporting these improvements to the plugin version, or document when to use each approach.


Premortem Analysis

Risk Likelihood Impact Status
Confusion between skill/plugin Medium Low Minor - documentation could clarify
/tmp permissions issues Very Low Low Standard location
Large repo timeouts Medium Medium Mitigated by --compress recommendation

Deployment Risk: Very Low - Markdown documentation only.


Verdict

✅ Approve - This is a valuable, well-documented skill that improves upon the existing plugin pattern. The minor markdown style suggestions from bots are either already addressed or not critical for a documentation file.


Updated review generated by Claude

@yamadashy yamadashy merged commit 7f87489 into main Jan 17, 2026
56 checks passed
@yamadashy yamadashy deleted the feat/add-repomix-explorer-skill branch January 17, 2026 10:36
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.

1 participant