repo-health-auditlisted

# Repo Health Audit ## Goal Produce a structured maintenance report that separates urgent repository risks from polish, identifies gaps in onboarding and automation, and recommends the next practical maintainer actions. ## When to use - The user asks whether a repository is healthy, maintainable, or ready to publish. - A repo needs a maintainer audit across docs, tests, CI, releases, and security hygiene. - The user wants a prioritized cleanup plan without immediate code edits. ## When not to use - The user asks for a focused PR review; use `pr-review`. - The task is only documentation clarity; use `docs-audit`. - The user already asked for implementation instead of audit. ## Inputs to inspect - README, docs, examples, changelog, license, security policy, and contribution guide. - Package files, lockfiles, test config, format/lint config, and validation scripts. - CI workflows, issue templates, release automation, and dependency update config. - Current `git status`, recent commits, and validation output when available. ## Review rubric Score docs, build/test, CI, release readiness, dependency hygiene, security baseline, issue/PR operations, and agent context from 0 to 5. Read `references/audit-rubric.md` for scoring detail and `references/report-template.md` for the report shape. ## Workflow 1. Inspect top-level files and repository structure. 2. Identify the main stack and validation commands. 3. Review docs against actual commands and files. 4. Check CI, releas