Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Data Analysis
Repomix Explorer
Use this skill when the user wants to analyze or explore a codebase (remote repository or local repository) using Repomix. Triggers on: 'analyze this repo',...
skill openclawclawhub Free
Use this skill when the user wants to analyze or explore a codebase (remote repository or local repository) using Repomix. Triggers on: 'analyze this repo',...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- kongyo2
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
User Intent Examples
The user might ask in various ways:
Remote Repository Analysis
"Analyze the yamadashy/repomix repository" "What's the structure of facebook/react?" "Explore https://github.com/microsoft/vscode" "Find all TypeScript files in the Next.js repo" "Show me the main components of vercel/next.js"
Local Repository Analysis
"Analyze this codebase" "Explore the ./src directory" "What's in this project?" "Find all configuration files in the current directory" "Show me the structure of ~/projects/my-app"
Pattern Discovery
"Find all authentication-related code" "Show me all React components" "Where are the API endpoints defined?" "Find all database models" "Show me error handling code"
Metrics and Statistics
"How many files are in this project?" "What's the token count?" "Show me the largest files" "How much TypeScript vs JavaScript?"
Your Responsibilities
Understand the user's intent from natural language Determine the appropriate repomix command: Remote repository: npx repomix@latest --remote <repo> Local directory: npx repomix@latest [directory] Choose output format (xml is default and recommended) Decide if compression is needed (for repos >100k lines) Execute the repomix command via shell Analyze the generated output using pattern search and file reading Provide clear insights with actionable recommendations
Step 1: Pack the Repository
For Remote Repositories: npx repomix@latest --remote <repo> --output /tmp/<repo-name>-analysis.xml IMPORTANT: Always output to /tmp for remote repositories to avoid polluting the user's current project directory. For Local Directories: npx repomix@latest [directory] [options] Common Options: --style <format>: Output format (xml, markdown, json, plain) - xml is default and recommended --compress: Enable Tree-sitter compression (~70% token reduction) - use for large repos --include <patterns>: Include only matching patterns (e.g., "src//*.ts,/*.md") --ignore <patterns>: Additional ignore patterns --output <path>: Custom output path (default: repomix-output.xml) --remote-branch <name>: Specific branch, tag, or commit to use (for remote repos) Command Examples: # Basic remote pack (always use /tmp) npx repomix@latest --remote yamadashy/repomix --output /tmp/repomix-analysis.xml # Basic local pack npx repomix@latest # Pack specific directory npx repomix@latest ./src # Large repo with compression (use /tmp) npx repomix@latest --remote facebook/react --compress --output /tmp/react-analysis.xml # Include only specific file types npx repomix@latest --include "**/*.{ts,tsx,js,jsx}"
Step 2: Check Command Output
The repomix command will display: Files processed: Number of files included Total characters: Size of content Total tokens: Estimated AI tokens Output file location: Where the file was saved (default: ./repomix-output.xml) Always note the output file location for the next steps.
Step 3: Analyze the Output File
Start with structure overview: Search for file tree section (usually near the beginning) Check metrics summary for overall statistics Search for patterns: # Pattern search (preferred for large files) grep -iE "export.*function|export.*class" repomix-output.xml # Search with context grep -iE -A 5 -B 5 "authentication|auth" repomix-output.xml Read specific sections: Read files with offset/limit for large outputs, or read entire file if small.
Step 4: Provide Insights
Report metrics: Files, tokens, size from command output Describe structure: From file tree analysis Highlight findings: Based on grep results Suggest next steps: Areas to explore further
Efficiency
Always use --compress for large repos (>100k lines) Use pattern search (grep) first before reading entire files Use custom output paths when analyzing multiple repos to avoid overwriting Clean up output files after analysis if they're very large
Output Format
XML (default): Best for structured analysis, clear file boundaries Plain: Simpler to grep, but less structured Markdown: Human-readable, good for documentation JSON: Machine-readable, good for programmatic analysis Recommendation: Stick with XML unless user requests otherwise.
Search Patterns
Common useful patterns: # Functions and classes grep -iE "export.*function|export.*class|function |class " file.xml # Imports and dependencies grep -iE "import.*from|require\\(" file.xml # Configuration grep -iE "config|Config|configuration" file.xml # Authentication/Authorization grep -iE "auth|login|password|token|jwt" file.xml # API endpoints grep -iE "router|route|endpoint|api" file.xml # Database/Models grep -iE "model|schema|database|query" file.xml # Error handling grep -iE "error|exception|try.*catch" file.xml
File Management
Default output: ./repomix-output.xml Use --output flag for custom paths Clean up large files after analysis: rm repomix-output.xml Or keep for future reference if space allows
Communication Style
Be concise but comprehensive: Summarize findings clearly Use clear technical language: Code, file paths, commands should be precise Cite sources: Reference file paths and line numbers Suggest next steps: Guide further exploration
Example 1: Basic Remote Repository Analysis
User: "Analyze the yamadashy/repomix repository" Your workflow: 1. Run: npx repomix@latest --remote yamadashy/repomix --output /tmp/repomix-analysis.xml 2. Note the metrics from command output (files, tokens) 3. Grep: grep -i "export" /tmp/repomix-analysis.xml (find main exports) 4. Read file tree section to understand structure 5. Summarize: "This repository contains [number] files. Main components include: [list]. Total tokens: approximately [number]."
Example 2: Finding Specific Patterns
User: "Find authentication code in this repository" Your workflow: 1. Run: npx repomix@latest (or --remote if specified) 2. Grep: grep -iE -A 5 -B 5 "auth|authentication|login|password" repomix-output.xml 3. Analyze matches and categorize by file 4. Read the file to get more context if needed 5. Report: "Authentication-related code found in the following files: - [file1]: [description] - [file2]: [description]"
Example 3: Structure Analysis
User: "Explain the structure of this project" Your workflow: 1. Run: npx repomix@latest ./ 2. Read file tree from output (use limit if file is large) 3. Grep for main entry points: grep -iE "index|main|app" repomix-output.xml 4. Grep for exports: grep "export" repomix-output.xml | head -20 5. Provide structural overview with ASCII diagram if helpful
Example 4: Large Repository with Compression
User: "Analyze facebook/react - it's a large repository" Your workflow: 1. Run: npx repomix@latest --remote facebook/react --compress --output /tmp/react-analysis.xml 2. Note compression reduced token count (~70% reduction) 3. Check metrics and file tree 4. Grep for main components 5. Report findings with note about compression used
Example 5: Specific File Types Only
User: "I want to see only TypeScript files" Your workflow: 1. Run: npx repomix@latest --include "**/*.{ts,tsx}" 2. Analyze TypeScript-specific patterns 3. Report findings focused on TS code
Error Handling
If you encounter issues: Command fails: Check error message Verify repository URL/path Check permissions Suggest appropriate solutions Large output file: Use --compress flag Use --include to narrow scope Read file in chunks with offset/limit Pattern not found: Try alternative patterns Check file tree to verify files exist Suggest broader search Network issues (for remote): Verify connection Try again Suggest using local clone instead
Help and Documentation
If you need more information: Run npx repomix@latest --help to see all available options Check the official documentation at https://github.com/yamadashy/repomix Repomix automatically excludes sensitive files based on security checks
Important Notes
Output file management: Track where files are created, clean up if needed Token efficiency: Use --compress for large repos to reduce token usage Incremental analysis: Don't read entire files at once; use grep first Security: Repomix automatically excludes sensitive files; trust its security checks
Self-Verification Checklist
Before completing your analysis: Did you run the repomix command successfully? Did you note the metrics from command output? Did you use pattern search (grep) efficiently before reading large sections? Are your insights based on actual data from the output? Have you provided file paths and line numbers for references? Did you suggest logical next steps for deeper exploration? Did you communicate clearly and concisely? Did you note the output file location for user reference? Did you clean up or mention cleanup if output file is very large? Remember: Your goal is to make repository exploration intelligent and efficient. Run repomix strategically, search before reading, and provide actionable insights based on real code analysis.
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md