codebase-vision-report

Analyzes a codebase by rendering it as dense images (via gitoutput's --images mode, which uses mdpix's bitmap-atlas renderer), reading every rendered page, and producing a report grounded in what was actually read. For a text-only, non-image variant, see codebase-text-report — same workflow shape, reads gitoutput's default .txt chunks instead of rendering pages.

Arguments

Invoke as /codebase-vision-report <target> :: <prompt>, or Skill(skill="codebase-vision-report", args="<target> :: <prompt>").

• target — a local directory path or a remote Git URL (anything gitoutput accepts as its source argument).
• prompt — the question or report focus (e.g. "find security issues", "summarize the architecture", "does this codebase handle X correctly").

Split args on the first ::. If no :: is present, treat the whole string as target and use a default prompt: "Summarize this codebase's architecture and key components."

Optional trailing flags in args (space-separated, after the prompt or anywhere in target): --image-profile <claude|gpt|gemini|grok> (default claude — this skill runs inside Claude Code, so claude is almost always correct), --exclude-pattern <glob> / --include-pattern <glob> (repeatable, passed through to gitoutput to scope a large codebase).

Step 1 — Generate images

Always invoke gitoutput at its densest defaults — claude profile and minification on — so the codebase packs into the fewest possible pages: never pass --no-minify, and only override --image-profile away from claude when the user explicitly names a different target model. Both are gitoutput's own defaults for --images, so simply omitting --image-profile/--no-minify already gets the minimum-page-count behavior; this is a deliberate choice, not an oversight, and following the command below exactly preserves it.