/plugadvpl:cobertura-doc

You can check Protheus documentation coverage by computing the percentage of functions that include Protheus.doc headers per module or source_type. This requires SQLite-backed indexed metadata to query and group the coverage data.

To prioritize ADVPL refactoring, you should sort documentation coverage results by lowest percentage first. This highlights modules or source types with the biggest documentation gaps, directing action to where Protheus.doc headers are most absent.

Yes, the documentation coverage analysis applies to large ADVPL and TLPP codebases. It identifies functions lacking Protheus.doc headers and calculates coverage percentages across both source code types.

You can find functions lacking Protheus.doc headers by grouping coverage by source category, such as mvc, rest, or cadastro. This is useful when module inference is incomplete, showing totals and documentation percentages.

Yes, you need SQLite-backed indexed metadata to analyze Protheus documentation gaps. The Skill relies on this database to compute coverage percentages and output actionable prioritization lists.

Protheus functions that cannot be mapped to a specific module are reported under a designated _sem_grupo entry. This ensures missing-module visibility is maintained during the documentation gap analysis.