project-health-checker

Health checks validate your project's critical components by automatically executing production secrets validation, configuration testing, and Genkit verification in sequence, then reporting a consolidated summary of results to identify problems quickly.

Yes, schedule health checks within your CI/CD workflow for regular, proactive monitoring. Running them automatically catches configuration drift, secrets mismanagement, and build failures before they reach production or staging environments.

Health checks validate production secrets integrity, test configurations, and Genkit runtime verification across development, QA, staging, and production environments, ensuring all critical components function as expected.

Run health checks as a first diagnostic step when encountering unexpected application behavior, during routine maintenance, or schedule them regularly in CI/CD pipelines to detect and prevent issues proactively.

Health checks consolidate validation of secrets, configurations, and Genkit verification into a single automated workflow, eliminating manual execution of separate diagnostic scripts and providing a unified summary report.

No, health checks orchestrate production-secrets-validator, test-configuration, and verify-genkit scripts into one automated workflow, eliminating the need to run each diagnostic tool separately and reducing debugging time.