codepack

codepack transforms directories into LLM-friendly text files.

A lightning-fast tool that converts the contents of a directory into a single, LLM-friendly text file, making it easy to process and analyze data with Large Language Models.

Installation

For detailed installation instructions, please visit the Codepack documentation.

Alternatively, you can follow the instructions below to install codepack.

Pre-built Binaries (Recommended)

Please see the documentation

Installation via Cargo (Optional)

Alternatively, you can install codepack from source with Rust's package manager cargo:

cargo install codepack

This will download, build, and install the latest version of codepack.

Quickstart

Once installed, simply run:

codepack /path/to/directory

By default, codepack will process the directory and output a .txt file with the contents of the files inside the directory. If you don't specify an output file, it will generate one based on the directory name and the number of files processed.

Features

• Lightning Fast: codepack is optimized for speed, ensuring that even large directories are processed efficiently.
• Customizable Output: Specify the output file name with the -o option, or let codepack generate one for you.
• Selective File Processing: Use the -e or --extension flag to include specific file types (e.g., .rs, .toml).
• File Exclusion: Exclude specific files or patterns with the -x or --excluded-files flag (e.g., .lock files, node_modules/).
• Suppress Output Prompt: If you don't want the default prompt in your output file, use the --suppress-prompt option.
• Powerful Filtering: Filter files based on file names, paths, and content using the -f or --filter option.

Filtering with codepack

Codepack supports three types of filters:

1. File Name Filters: Filter files based on their names using the file.name= prefix followed by the pattern to match.

Example: codepack -f "file.name=main.py" /path/to/project (includes only files named "main.py")

2. Path Contains Filters: Filter files based on a substring present anywhere in their path using the path.contains= prefix followed by the substring.

Example: codepack -f "path.contains=src" . (includes only files within the "src" directory and its subdirectories)

3. Content Contains Filters: Filter files based on a substring present in their content using the content.contains= prefix followed by the substring.

Note: Content filters are applied after the file has been read, so this can be slower than other filter types.

Example: codepack -f "content.contains=function" /path/to/code (includes only files containing the word "function")

You can combine multiple filters using multiple -f or --filter options. Codepack uses OR logic for filtering, so a file will be included if it matches any of the provided filters.

Usage

codepack [OPTIONS] <DIRECTORY_PATH>

Options:
  -o, --output <OUTPUT>          Output file path (optional)
  -e, --extension <EXTENSIONS>   File extensions to include (e.g., -e rs -e toml)
  -x, --excluded-files <FILES>   Files to exclude by name/pattern (e.g., -x *.lock -x node_modules/)
  -f, --filter <FILTERS>         Filter files by name, path, or content (e.g., -f "file.name=main.rs")
      --suppress-prompt          Suppress the output prompt
  -h, --help                     Print help
  -V, --version                  Print version

Examples

Convert a directory to a .txt file with a custom output name:

codepack /path/to/my/code -o my_code.txt

Process only .rs and .toml files from a directory:

codepack /path/to/my/code -e rs -e toml

Exclude lock files and node_modules:

codepack /path/to/my/code -x "*.lock" -x "node_modules/"

Contributing

We welcome contributions to codepack! Please feel free to submit issues or pull requests on GitHub.

License

codepack is distributed under the terms of the GPL-3.0 License. See the LICENSE file for details.