Inspectors reference#

Inspectors describe the shape of content and return evidence: counts and distributions, never recommendations. They are the descriptive dual of check types and drive the inspect command. They come in two layers: raw-source inspectors profile a store before configuration, collection inspectors profile a configured collection. These pages are generated from the inspector registry, so they always match the shipped binary.

Raw-source inspectors#

Raw-source inspectors profile a backend store directly, before any collection configuration: what files are present, how they parse, and how they are named.

• File tree: Map files, directories, extensions, regions, and filename conventions, opening no files.
• File content shape: Profile selected files by text, tabular, and tree content structure.

Collection inspectors#

Collection inspectors profile a configured collection’s items, probing them through the same substrate the checks use.

• Object fields: A data dictionary over item frontmatter: per-field presence, types, cardinality, and common values.
• Markdown body: Body conventions across items: heading shape and recurring sections.