test-check

Post-change validation and log audits are automated by reading test commands from .claude/project.json, selectively running frontend, backend, and end-to-end tests based on file changes, and reporting failures with guardrails to prevent marking work complete.

Selective end-to-end tests run by reading configuration from .claude/project.json and executing only the specified test hooks relevant to the changed files, gracefully skipping any steps that are not configured in the project setup.

Post-change testing works with partial configurations by gracefully skipping frontend or end-to-end steps that are not specified in .claude/project.json, executing only the backend tests and logging their audit results.

Log audits integrate by running before and after tests to surface failures and ensure a clean state, providing guardrails that report a clear failure if any test step or audit check fails during the validation workflow.

Automated guardrails prevent marking work as complete on test failures by reporting a clear failure when any validation step fails, ensuring that post-change tests and log audits must pass before a commit or PR merge is considered successful.

Missing test steps are gracefully skipped without failing the workflow by checking .claude/project.json for configured commands, ensuring post-change validation only runs specified tests and omits unconfigured frontend, backend, or end-to-end checks.