What is a 'Reference Class' in this context?

A reference class categorizes your repository (e.g., as a production service vs. a prototype) so the health assessment is calibrated to realistic expectations rather than absolute, arbitrary standards.

How does it handle missing documentation or tooling?

It uses a 'Coverage Manifest' to explicitly name unknowns, documenting what couldn't be assessed and why, which prevents users from making decisions based on silent exclusions.

Does Review-Health modify my code?

No, Review-Health is strictly advisory. It focuses on observation and orientation to provide a strategic map, making no changes to the source code.

When should I use this instead of a standard linter?

Use Review-Health for high-level strategic planning and situational awareness during onboarding or evaluation, whereas linters are used for tactical, file-level code quality.

Review-Health Repository Assessment

Name: Review-Health Repository Assessment
Author: chrisallenlane

bychrisallenlane

•

Herramientas para Desarrolladores

Conducts a strategic, evidence-based health review of software repositories to guide engagement and investment decisions.

Review-Health is a strategic orientation skill designed for developers who have inherited new projects, are evaluating open-source libraries, or need to assess their own project's state. It follows a rigorous OODA (Observe, Orient, Decide, Act) methodology to provide a neutral, evidence-cited map of a repository's health without making direct changes. By calibrating findings against specific reference classes—such as production services, research prototypes, or libraries—it helps users overcome inheritor's paralysis and identifies exactly where to focus effort or exercise caution.

Características Principales

0112 GitHub stars

02Systematic OODA-based orientation framework to prevent cognitive bias

03Strategic engagement routing to specialized refactoring or security skills

04Evidence-cited findings with specific file and line-number references

05Reference-class calibration to ensure evaluations match project goals

06Comprehensive Coverage Manifest documenting missing signals and tools

Casos de Uso

01Performing strategic internal audits to identify technical debt hotspots

02Evaluating third-party or FOSS projects for production adoption

03Onboarding to an inherited or legacy codebase with unknown risks

Características Principales

0112 GitHub stars

02Systematic OODA-based orientation framework to prevent cognitive bias

03Strategic engagement routing to specialized refactoring or security skills

04Evidence-cited findings with specific file and line-number references

05Reference-class calibration to ensure evaluations match project goals

06Comprehensive Coverage Manifest documenting missing signals and tools

Casos de Uso

01Performing strategic internal audits to identify technical debt hotspots

02Evaluating third-party or FOSS projects for production adoption

03Onboarding to an inherited or legacy codebase with unknown risks