go-local-health

Run Go health checks by executing non-interactive scripts from the repository root to validate tests, coverage, and lint in Go projects containing go.mod and go.sum files.

Yes, checking your Go project requires language-tool chains including go, tparse, and golangci-lint to execute strict non-interactive health checks and parse test outputs.

Repeatable Go test and coverage snapshots are generated by running deterministic, non-interactive health checks that provide consistent results for iterative test loops.

Yes, you can use it for quick health snapshots in Go repositories to validate project status at a glance, provided the repository contains a go.mod file.

Go health checks require non-interactive execution to ensure deterministic behavior, allowing reliable and repeatable validation of tests, coverage, and lint in CI environments.