ck:repomix

Pack local or remote Git repositories into single XML, Markdown, JSON, or plain-text files.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-repomix-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:repomix
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/repomix
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-repomix-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Large codebases and third-party repositories are difficult to feed into LLMs or audit manually because of size, sensitive files, and inconsistent formats; repomix consolidates and formats repositories into single, AI-friendly files so you can analyze, review, or audit code with an LLM or automation toolchain.

Core Features & Use Cases

  • Repository packaging: Produce XML, Markdown, JSON, or plain-text snapshots that preserve file hierarchy and metadata for LLM consumption.
  • Remote and local support: Process local folders or remote GitHub repositories (via npx) and optionally target specific commits.
  • Token management & filtering: Count tokens per file, produce token trees, and include/exclude files using globs and .repomixignore rules to stay within LLM context limits.
  • Security-aware processing: Optional secret scanning and comment removal, plus configuration to ignore sensitive files before sharing outputs.
  • Batch automation: scripts/repomix_batch.py enables batch processing, environment-based configuration, progress reporting, and CI integration.

Quick Start

Use repomix to package the current repository into a markdown snapshot ready for LLM analysis.

Frequently Asked Questions about ck:repomix

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

FAQPage Schema
How do I package a codebase into a single file for LLM context?

Pack a codebase into a single LLM context file by consolidating repository contents into XML, Markdown, JSON, or plain text snapshots that preserve file hierarchy and metadata. This process formats local folders or remote Git repositories for AI consumption.

Can I package a remote GitHub repository for an LLM security audit?

Yes, you can package remote GitHub repositories via npx, optionally targeting specific commits. This allows you to prepare third-party or large codebases for LLM security audits and codebase comparisons without cloning them locally first.

How do I count tokens per file to stay within LLM context limits?

Count tokens per file and produce token trees to manage LLM context limits effectively. You can also include or exclude specific files using globs and .repomixignore rules to ensure the packaged snapshot fits your model's context window.

Does repomix respect .gitignore rules when creating code snapshots?

Yes, creating code snapshots with repomix respects .gitignore rules, along with custom .repomixignore configurations. This ensures sensitive files are properly ignored and excluded from the final AI-ready output before sharing it with LLMs.

What is the best way to automate repository packaging for multiple projects?

Automate repository packaging for multiple projects using batch processing scripts that enable environment-based configuration, progress reporting, and CI integration. This allows you to systematically generate AI-friendly snapshots across various repositories.

Can I remove comments and scan for secrets before sharing a codebase snapshot?

Yes, you can remove comments and perform secret scanning before sharing a codebase snapshot. These security-aware processing options help sanitize the AI-ready output, ensuring sensitive information is stripped from the consolidated file.