home / skills / jackspace / claudeskillz / repomix_mrgoonie

repomix_mrgoonie skill

/skills/repomix_mrgoonie

This skill packages entire codebases into AI-friendly files, preserving structure, enabling token-aware formats for rapid analysis and audits.

This is most likely a fork of the repomix skill from mamba-mental
npx playbooks add skill jackspace/claudeskillz --skill repomix_mrgoonie

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
5.5 KB
---
name: repomix
description: Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
---

# Repomix Skill

Repomix packs entire repositories into single, AI-friendly files. Perfect for feeding codebases to LLMs like Claude, ChatGPT, and Gemini.

## When to Use

Use when:
- Packaging codebases for AI analysis
- Creating repository snapshots for LLM context
- Analyzing third-party libraries
- Preparing for security audits
- Generating documentation context
- Investigating bugs across large codebases
- Creating AI-friendly code representations

## Quick Start

### Check Installation
```bash
repomix --version
```

### Install
```bash
# npm
npm install -g repomix

# Homebrew (macOS/Linux)
brew install repomix
```

### Basic Usage
```bash
# Package current directory (generates repomix-output.xml)
repomix

# Specify output format
repomix --style markdown
repomix --style json

# Package remote repository
npx repomix --remote owner/repo

# Custom output with filters
repomix --include "src/**/*.ts" --remove-comments -o output.md
```

## Core Capabilities

### Repository Packaging
- AI-optimized formatting with clear separators
- Multiple output formats: XML, Markdown, JSON, Plain text
- Git-aware processing (respects .gitignore)
- Token counting for LLM context management
- Security checks for sensitive information

### Remote Repository Support
Process remote repositories without cloning:
```bash
# Shorthand
npx repomix --remote yamadashy/repomix

# Full URL
npx repomix --remote https://github.com/owner/repo

# Specific commit
npx repomix --remote https://github.com/owner/repo/commit/hash
```

### Comment Removal
Strip comments from supported languages (HTML, CSS, JavaScript, TypeScript, Vue, Svelte, Python, PHP, Ruby, C, C#, Java, Go, Rust, Swift, Kotlin, Dart, Shell, YAML):
```bash
repomix --remove-comments
```

## Common Use Cases

### Code Review Preparation
```bash
# Package feature branch for AI review
repomix --include "src/**/*.ts" --remove-comments -o review.md --style markdown
```

### Security Audit
```bash
# Package third-party library
npx repomix --remote vendor/library --style xml -o audit.xml
```

### Documentation Generation
```bash
# Package with docs and code
repomix --include "src/**,docs/**,*.md" --style markdown -o context.md
```

### Bug Investigation
```bash
# Package specific modules
repomix --include "src/auth/**,src/api/**" -o debug-context.xml
```

### Implementation Planning
```bash
# Full codebase context
repomix --remove-comments --copy
```

## Command Line Reference

### File Selection
```bash
# Include specific patterns
repomix --include "src/**/*.ts,*.md"

# Ignore additional patterns
repomix -i "tests/**,*.test.js"

# Disable .gitignore rules
repomix --no-gitignore
```

### Output Options
```bash
# Output format
repomix --style markdown  # or xml, json, plain

# Output file path
repomix -o output.md

# Remove comments
repomix --remove-comments

# Copy to clipboard
repomix --copy
```

### Configuration
```bash
# Use custom config file
repomix -c custom-config.json

# Initialize new config
repomix --init  # creates repomix.config.json
```

## Token Management

Repomix automatically counts tokens for individual files, total repository, and per-format output.

Typical LLM context limits:
- Claude Sonnet 4.5: ~200K tokens
- GPT-4: ~128K tokens
- GPT-3.5: ~16K tokens

## Security Considerations

Repomix uses Secretlint to detect sensitive data (API keys, passwords, credentials, private keys, AWS secrets).

Best practices:
1. Always review output before sharing
2. Use `.repomixignore` for sensitive files
3. Enable security checks for unknown codebases
4. Avoid packaging `.env` files
5. Check for hardcoded credentials

Disable security checks if needed:
```bash
repomix --no-security-check
```

## Implementation Workflow

When user requests repository packaging:

1. **Assess Requirements**
   - Identify target repository (local/remote)
   - Determine output format needed
   - Check for sensitive data concerns

2. **Configure Filters**
   - Set include patterns for relevant files
   - Add ignore patterns for unnecessary files
   - Enable/disable comment removal

3. **Execute Packaging**
   - Run repomix with appropriate options
   - Monitor token counts
   - Verify security checks

4. **Validate Output**
   - Review generated file
   - Confirm no sensitive data
   - Check token limits for target LLM

5. **Deliver Context**
   - Provide packaged file to user
   - Include token count summary
   - Note any warnings or issues

## Reference Documentation

For detailed information, see:
- [Configuration Reference](./references/configuration.md) - Config files, include/exclude patterns, output formats, advanced options
- [Usage Patterns](./references/usage-patterns.md) - AI analysis workflows, security audit preparation, documentation generation, library evaluation

## Additional Resources

- GitHub: https://github.com/yamadashy/repomix
- Documentation: https://repomix.com/guide/
- MCP Server: Available for AI assistant integration

Overview

This skill packages entire code repositories into single, AI-friendly files using Repomix. It preserves file context and structure while offering customizable include/exclude patterns, comment removal, token counting, and multiple output formats (XML, Markdown, JSON, plain). Use it to prepare repository snapshots optimized for LLM consumption, security review, or documentation generation.

How this skill works

Repomix scans a local or remote repository, applies include/exclude patterns and .gitignore rules, and extracts files into a single formatted output. It can remove comments, run secret detection, count tokens per file and total output, and emit outputs in several formats with optional headers and summaries. The tool reports token budgets and security warnings so you can tailor the package for a target LLM.

When to use it

  • Prepare a repository snapshot to feed into an LLM for code review or architecture analysis
  • Package third-party libraries for security audits or dependency inspections
  • Create compact context files for documentation generation or automated summarization
  • Investigate bugs across many files by extracting only relevant modules
  • Produce token-aware inputs for models with strict context limits

Best practices

  • Define precise include patterns to limit output to relevant files and reduce tokens
  • Enable security checks and review outputs before sharing; use .repomixignore for secrets
  • Use comment removal when you need minimal token usage and the code remains understandable
  • Select an output format that matches your workflow (Markdown for docs, XML/JSON for tooling)
  • Monitor token counts against your target LLM and split packages if needed

Example use cases

  • Package a feature branch (src/**) into a Markdown file for an AI-assisted code review
  • Create an XML snapshot of a vendor library for a security audit pipeline
  • Generate a plain-text context file trimmed to auth and API modules for bug triage
  • Collect code and docs (src/**, docs/**, *.md) into a single file to feed a documentation generator
  • Pull a remote repo at a specific commit and produce a token-counted output for an LLM

FAQ

Can Repomix process remote repositories without cloning?

Yes. Repomix can fetch and package remote repositories by URL or shorthand (owner/repo) and can target specific commits.

How do I avoid leaking secrets in a packaged file?

Enable the built-in security checks, add sensitive paths to .repomixignore, avoid packaging .env files, and review output before sharing.