codebase-text-report
codebase-text-report
Analyzes a codebase by ingesting it as plain-text chunks via gitoutput's default (non-image) mode, reading every chunk, and producing a report grounded in what was actually read. This is the regular, text-only counterpart to the codebase-vision-report skill, which instead renders the codebase as dense PNG pages via mdpix for token-efficient image-based reading — use that one if you want the image-packing pipeline instead.
Arguments
Invoke as /codebase-text-report <target> :: <prompt>, or Skill(skill="codebase-text-report", args="<target> :: <prompt>").
target— a local directory path or a remote Git URL (anythinggitoutputaccepts as itssourceargument).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: --exclude-pattern <glob> / --include-pattern <glob> (repeatable, passed through to gitoutput to scope a large codebase). There is no image-profile equivalent in text mode.
Step 1 — Generate text chunks
Run gitoutput via npx with --json (no --images) so the result is machine-parseable, writing to a fresh output base name (use a timestamp or the target's basename plus a short random suffix to avoid colliding with a prior run of this skill in the same working directory):