vcrepomix

# Repomix Repomix packs repositories into AI-friendly artifacts for read-only reference work. This is a helper skill only. - Do use it for research, audits, source comparison, documentation context, bug investigation prep, and feature-porting prep. - Do not use it to create plans, decide execution scope, or bypass RIPER approval. - Do not write outputs into plan-control folders like `process/general-plans/active/` or `process/features/*/active/`. ## When To Use Use this skill when you need: - a local repo snapshot for LLM review - a remote GitHub repo pack without cloning it deeply - a focused module pack for debugging or architectural comparison - a documentation or API-context pack - a security-oriented repository review artifact - a reusable reference artifact for a later helper such as `xia` If the task only needs a few files, ordinary `rg` plus targeted reads is cheaper than `repomix`. ## Output Policy Generated artifacts belong in the project's `references/` folders only: - General or cross-cutting work: - `process/general-plans/references/` - Feature-scoped work: - `process/features/{feature}/references/` Keep outputs flat by default unless the user explicitly asks for a dedicated subfolder. Suggested filenames: - `repomix-{topic}-{dd-mm-yy}.xml` - `repomix-{topic}-{dd-mm-yy}.md` - `repomix-{topic}-{dd-mm-yy}.txt` - `repomix-{topic}-{dd-mm-yy}.json` Prefer a short topic slug over a generic `output` name. ## Install And Invocation Use `pnpm`-aligned ...