skill-cross-product-check

Downstream Qt product documentation breakages occur when module changes rename pages, titles, filenames, APIs, or QML types. Identifying these reference changes early prevents broken links and ensures safer releases across doc.qt.io and marketing pages.

Verify cross-product documentation references by running an audit during the documentation change review. This generates a prioritized verification workflow reporting snapshot paths, index file availability, and per-product link mechanisms to guide remediation.

Yes, cross-product verification supports doc-snapshots.qt.io and qt.io marketing pages alongside doc.qt.io. It assesses reference impacts from module changes across these platforms to document and help fix downstream breakages.

The best way to track QML type renames is applying a cross-product reference check across Qt documentation properties. This audits affected links, verifies snapshot paths, and outputs a prioritized workflow to remediate broken references.

Verification is limited to assessing page renames, title changes, filename changes, API renames, and QML type renames. It reports per-product link mechanisms and index availability, but does not automatically fix the broken references it discovers.