repo-health

A repository health sweep aggregates dead-code detection, test status, dependency audits, secret scanning, and gotchas tracking into a single scored report. You can trigger it by asking Claude Code or Copilot to run the health sweep on an active Git repository.

A repo health check report includes a unified score from parallel checks covering dead-code, test results, dependency vulnerabilities, exposed secrets, and outdated gotchas. It also generates a .claude/.next-action file suggesting the highest-impact maintenance task.

Yes, repo health sweeps are designed for pre-release hygiene validation. They surface high-risk items across dependencies, secrets, and tests early, providing a clear next-action hint to resolve critical issues before deployment.

By running parallel checks on dead-code, tests, dependencies, secrets, and gotchas, the sweep produces a scored roll-up report and writes a .claude/.next-action suggestion for the single highest-impact maintenance task to prioritize.

The repo health sweep operates in read-only mode to analyze repository hygiene without altering code. It aggregates issues into a scored report and outputs a next-action suggestion file without performing automatic fixes.

Running an automated repo health sweep scans Git repositories for exposed secrets and dependency vulnerabilities alongside dead-code and test status. It consolidates findings into a single scored report with actionable maintenance priorities.