# Repomix — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/repomix

A repository packet should be portable and deliberate about what it includes.

## What we admire

Repomix made repo-to-prompt packaging concrete, with explicit formats, filters, and output that can travel between tools. It set a high bar for making source context shareable without requiring a live index.

## The principle that stayed

Packaging is useful only when selection, omission, and size are visible. An enormous serialized repo can hide what mattered just as easily as a tiny, under-scoped excerpt.

## Where CodeVetter stands

Repo Unpack and evidence bundles use bounded, structured artifacts tied to a revision. Repomix was evaluated as an optional adapter, not chosen as the review engine or a required dependency.

## Sources

- [Repomix source repository](https://github.com/yamadashy/repomix) — the creator's own source
- [CodeVetter OSS integration decision](https://github.com/Codevetter/codevetter/blob/main/docs/architecture/decisions/oss-integration.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)