repo-status

To generate a repository health assessment, apply a status audit tool to your local or cloned code repository path. It produces a single .status.md file combining filesystem inventory, semantic clustering, file importance ranking, and health checks for rapid onboarding.

Creating a codebase overview document for handoffs is best done by generating a structured .status.md file. This file maps semantic clusters, enumerates packages, and ranks file criticality to provide an immediate, navigable snapshot for the receiving developer.

Yes, you can audit repository health without external dependencies because the status generation process requires only read access to the repository path and basic file listing and line counting capabilities, along with optional semantic cluster references for mapping.

Semantic clustering during a repository audit works by mapping codebase components to behavioral verbs, producing component tables, identifying orphans, and ranking files into criticality tiers to build an accurate mental model before deep refactoring work.

A pre-refactor planning file inventory should include parallel file counts, lines of code estimates, package and module enumeration, and per-layer status for frontend, backend, infrastructure, and documentation to accurately ground the refactoring scope.

You need a single-file repository status document when you require an immediate, navigable snapshot for onboarding, periodic health checks, handoffs, or pre-refactor planning, combining filesystem metrics and security checks into one structured overview.