probare

To check if a file contains executable code or prose descriptions, you analyze its substance density by parsing executable forms against prose text. This evaluation outputs a structured verdict classifying the content type and highlighting any placeholders.

Static analysis for documentation quality evaluates file content to determine its true substance by parsing executable forms versus prose. It detects placeholders and TODOs, checks alignment with declared purpose, and provides structured decision guidance.

You detect placeholders and TODOs in source code and design documents by running content honesty checks. This analysis scans for alignment gaps between declared purpose and actual content, highlighting incomplete sections and evaluating form density.

Yes, you can evaluate form density in README files to determine if they are substantive. Analyzing the ratio of executable forms to prose descriptions classifies whether the file contains a substantive program or merely prose documentation.

You need to run a substance analysis on specifications when preventing the misinterpretation of documentation. It determines whether a spec file contains executable code or prose descriptions, identifies alignment gaps with declared purpose, and suggests restructuring next steps.

A limitation of code detection in prose-heavy specification files is its focus on substance density and form parsing rather than logic validation. While it highlights placeholders and TODOs, it does not execute or validate the detected executable forms.