repomix

Package code repositories into single XML, Markdown, JSON, or plain text files.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/HsnSaboor/open-engineer --skill repomix-hsnsaboor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repomix
Source: https://github.com/HsnSaboor/open-engineer/tree/main/src/skills/bundled/samhvw8-repomix
Command: npx skills add https://github.com/HsnSaboor/open-engineer --skill repomix-hsnsaboor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of preparing entire code repositories for analysis by Large Language Models (LLMs), making it easier to feed complex codebases into AI tools.

Core Features & Use Cases

  • Repository Packaging: Converts entire codebases into single, AI-friendly files.
  • AI Context Generation: Creates optimized input for LLMs like Claude, ChatGPT, and Gemini.
  • Use Case: You need to provide a large React project to an AI for a security audit. Use Repomix to package the entire project into a single Markdown file, ensuring all relevant code and configurations are included and formatted for AI consumption.

Quick Start

Use repomix to package the current directory into a markdown file named 'repo-context.md'.

Frequently Asked Questions about repomix

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

FAQPage Schema
How do I package an entire code repository into a single file for AI analysis?

To package a code repository for AI analysis, you can use a tool to consolidate local or remote codebases into a single file. This process aggregates all relevant code and configurations into formats like XML, Markdown, JSON, or plain text optimized for LLM consumption.

What is the best way to provide a large React project to an LLM for a security audit?

The best way to provide a large project for an AI security audit is to package the entire codebase into a single Markdown file. This ensures all relevant code and configurations are included and formatted specifically for AI consumption and context generation.

Can I count tokens before feeding a packaged codebase snapshot into an LLM?

Yes, you can count tokens when preparing a codebase snapshot for an LLM. The packaging process includes token counting features to help you measure and manage the context size before passing the aggregated repository file to AI assistants.

Does repository packaging for AI context generation support remote GitHub repositories?

Repository packaging for AI context generation supports both local and remote repositories. You can aggregate code from remote sources directly into AI-friendly files without needing to manually clone and traverse the entire project structure first.

What output formats are available when converting a codebase into an AI-friendly file?

Available output formats for converting a codebase include XML, Markdown, JSON, and plain text. These formats are designed to be AI-friendly, allowing LLMs like Claude, ChatGPT, and Gemini to easily parse and analyze the packaged code.

Why should I remove comments when packaging code for LLM context generation?

Removing comments when packaging code for LLM context generation reduces file size and token count, ensuring the AI focuses strictly on the executable code. This streamlines the input for security audits and complex codebase analysis.