quick-check

To run sanity checks before a commit, execute a quick validation command in your project root to surface obvious issues like empty handlers, failing builds, and missing tests across your repository.

The best way to validate builds and tests is to run an automated check that detects your package.json, executes the build and test scripts, and provides a concise pass/fail summary of the repository state.

Yes, you can check git status and codebase integrity without making changes by running a read-only sanity check that reports empty handlers, build results, and repository status without modifying files.

Yes, a pre-merge sanity check works without external dependencies because it natively detects project setups like package.json to run builds, execute tests, and display git status.

A codebase sanity check catches common development problems like empty handlers, stale dependencies, failing builds, and missing tests to surface 80% of obvious issues early.

You need to run a quick validation check during development, before commits, or pre-merge to verify basic integrity, confirm builds pass, and ensure tests run successfully across common project setups.