scan-report
Summarize repository scan shape with largest files, extensions, skip reasons, and chunk counts.
Syntax#
clyde scan-report REPO [scan flags] [--json] [--top N]Options#
| Flag | Purpose |
|---|---|
--json | Print a machine-readable repository scan report. |
--top | Number of largest included files to show. |
--include | Only include matching globs; repeatable. |
--exclude | Skip matching globs in addition to defaults; repeatable. |
--max-file-bytes | Skip files larger than this many bytes. |
--max-chunk-chars | Split source text at this many characters. |
Arguments#
REPOis the repository path to scan.
Examples#
clyde scan-report .clyde scan-report . --jsonclyde scan-report . --include "internal/**/*.go" --top 20Example Use Cases#
Use scan-report when a human, CI job, or AI assistant needs compact repository-shape context before running agent, bundle, or sync. The report includes included/skipped counts, chunk count, largest included files, extension counts, skip reasons, and scan limits.
Safety Notes#
scan-report is read-only. It does not write bundle files, upload source, or contact Ollama or NotebookLM.