project-checker

A project health check diagnoses your codebase across multiple dimensions: documentation completeness (README, CHANGELOG, LICENSE), Memory Bank files (activeContext.md, progress.md, decisionLog.md), DDD architecture conformance, code quality via linting, test coverage, and Git state. Run the Skill on your repository to identify gaps before release or onboarding.

Health checks validate presence of core documentation files (README, CHANGELOG, LICENSE), Memory Bank status tracking files (activeContext.md, progress.md, decisionLog.md), DDD compliance, code quality metrics via lint and syntax validation, test coverage levels, and Git repository state to ensure project completeness.

Run health checks during pre-release validation, when onboarding new contributors to verify documentation and architecture clarity, and during ongoing maintenance cycles to catch quality drift. Early detection of missing documentation, architectural gaps, and test coverage issues prevents larger problems downstream.

Yes. Health checks perform code quality assessment through lint validation, syntax verification, and test coverage measurement. Combined with architecture governance checks and documentation audits, they provide a multi-dimensional view of project health beyond code alone.

DDD (Domain-Driven Design) conformance validates your project's architectural structure against DDD principles. Health checks include DDD compliance verification to ensure your codebase maintains clear domain boundaries, preventing architectural decay and supporting long-term maintainability.

No. Health checks identify what documentation is missing—README, CHANGELOG, LICENSE, and Memory Bank files—making them most valuable on projects lacking complete documentation. The audit reveals exactly what gaps exist, guiding your next documentation and quality improvement efforts.