Repomix Code Analysis

Use Repomix to pack a repository into a single AI-friendly file (usually XML), then ask the user to run the analysis in a large-context model (Gemini) and paste back the result.

Default behavior: broad strokes first. Do a quick whole-repo measurement pass, then re-pack with obvious non-code/unrelated noise excluded. If that filtered whole-repo pack fits within ~1,000,000 tokens, do not over-optimize—hand it off to Gemini.

Non-negotiables

• Treat Repomix output files as read-only artifacts. Make changes only in the original repo files.
• Keep Repomix security checks enabled by default. Use --no-security-check only if the user explicitly requests it and confirms the output is safe to share externally.
• If packing a remote repo is required but network/git access is blocked by the sandbox, ask the user to run outside the sandbox.
• Do not open/search the Repomix output (XML) before Gemini handoff. Decide what to exclude using only token stats + folder/filename paths.
• Exception: only do a targeted search when the user explicitly asks to find a specific known identifier.

Workflow