Copying the info from the Summit talk:

Benjamin Ihrig (SAP SE) / Repository Linter@SAP
At SAP, InnerSource practices are increasingly becoming adopted as an essential part of our software development process, promoting collaboration, innovation and efficient code reuse. Ensuring consistency and quality across numerous repositories is challenging. To address this, we built an internal repository linter to standardize configurations and InnerSource-relevant content, while also providing automated fixes for detected issues. This session will share our journey of developing and piloting this tool to enhance repository quality and uniformity. Participants will gain insights into the rationale behind the linter, its implementation and the standards it aims to enforce.

Is this idea more suitable for an entirely new pattern, or could it be expressed as multiple smaller extensions to existing patterns?

Elaborating on the latter:

For the Standard Base Documentation we could add text like

You can make it easier for your users to stick to these standard files by offering a linter that will do XYZ