oss-repository-conventions

Purpose

Helps a maintainer reach and hold a high-quality open-source repository. Routes each request to the capability for the domain in question, and runs each in the mode the request implies — scan, audit, or scaffold.

Operating modes

Every capability supports the same three modes; the router picks the one the request implies, defaulting to audit when ambiguous.

Mode	Question it answers	Writes files?
scan	"What does this repo declare today?"	No
audit	"How does it measure up, and what's missing or weak?"	No
scaffold	"Create the missing/upgraded file."	Yes — one confirmation per file

scan is the read-only inventory + summary the skill has always done — extract declared rules, cite the file of truth, flag conflicts.
audit layers judgment on the scan: score against references/oss-health-rubric.md and references/house-style.md, classify each gap must / should / could, and explain why it matters for an OSS project.
scaffold acts on an audit finding: propose file content from the templates a capability carries, show it, and write only on explicit confirmation. Never bulk-writes; never overwrites an existing file without showing a diff first.