software-repository-guidelineslisted

# Repository Health Audit Run this skill only when the user explicitly asks to assess, bootstrap, or harden a repository. It is an audit, not a routine development gate. Do not invoke it from another skill and do not turn an ordinary feature, bug fix, or review into a repository-wide hardening project. ## Process 1. Establish the audit scope with the user: full repository, or one of developer experience, validation and CI, security, documentation, or release readiness. 2. Inspect the repository and load `references/00-overview.md` plus only the references relevant to that scope. Load every reference only for a requested full audit. 3. Gather evidence from version-controlled files, canonical commands, CI configuration, and provider configuration when the user authorizes access. Do not treat an assertion as evidence. 4. Classify every inspected item as `complete`, `gap`, `not applicable`, `deferred`, or `accepted risk`. A complete item satisfies the evidence rule in `references/00-overview.md`. 5. Return a compact report. Do not edit repository files unless the user separately asks to plan or implement selected recommendations. ## Output Include: - audit scope and references loaded; - evidence-backed complete items; - gaps, each with impact, evidence, and smallest recommended remediation; - not-applicable items and their repository-specific reason; - deferred and accepted-risk items with an owner or recorded user rationale; - a prioritized shortlist of inde