repomix-explorer

Pack local or remote repositories with Repomix CLI and analyze the generated output.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/369sup/support --skill repomix-explorer-369sup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repomix-explorer
Source: https://github.com/369sup/support/tree/main/plugins/repomix-context/skills/repomix-explorer
Command: npx skills add https://github.com/369sup/support --skill repomix-explorer-369sup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires repomix.

What problem does it solve? Understanding an unfamiliar or large codebase is slow when you have to open files one by one. This Skill packs an entire repository into a single searchable file using the Repomix CLI, then searches and reads that output to answer structural, pattern, and metrics questions quickly. ## Core Features & Use Cases - Remote and Local Packing: Analyze any GitHub repository via --remote or pack a local directory, with output written to a temporary location outside the working tree. - Pattern Discovery: Use rg searches over the packed output to find authentication code, API endpoints, React components, database models, or error handling across many files. - Metrics and Structure: Report file counts, token estimates, largest files, and language breakdowns, plus file-tree overviews for architecture understanding. - Use Case: A user asks "What's the structure of facebook/react?" The Skill runs Repomix with compression, searches the output for exports and entry points, and returns a structural summary with file references. ## Quick Start Ask the assistant to analyze the repository at a GitHub URL or local path and summarize its structure, main components, and token count.

Frequently Asked Questions about repomix-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a GitHub repository without cloning it?▼

Run Repomix with the --remote flag followed by the owner/repo name or URL, and direct output to a temporary file. The packed result can then be searched with ripgrep to explore structure, patterns, and metrics without a local clone.

How do I find all authentication code across a large codebase?▼

Pack the repository with Repomix using a narrow include scope, then run ripgrep with case-insensitive patterns like auth, login, password, or token over the output file. Use context flags to see surrounding lines and cite file paths in findings.

When should I use Repomix compression for repository analysis?▼

Use the --compress flag for repositories larger than about 100k lines. Tree-sitter compression reduces token count by roughly 70 percent while keeping signatures and structure, making large repos like facebook/react practical to analyze.

When should I not use Repomix to explore a codebase?▼

Avoid packing when a known file, symbol, or module can answer the question directly with file reads or ripgrep. It is also not suited for editing code, running tests, git operations, or single-symbol lookups in the local project.

Is it safe to pack a repository that may contain secrets?▼

Repomix security scanning alone is not sufficient. Explicitly exclude environment files, credentials, keys, certificates, dependency stores, and build output before packing, and review the selected file list before sharing any output.