smoke-test

Run a post-restart smoke test for gbrain and OpenClaw services using the command `gbrain smoke-test` after any container restart. This verifies critical services are up and automatically resolves known issues found during the check.

Post-restart health checks for OpenClaw environments automatically verify critical services are running and apply auto-fixes for known issues. Users can also define custom test scripts to extend the automated health verification coverage.

Yes, you can add custom test scripts to the gbrain smoke test. The skill supports extensible test scripts, allowing users to define custom checks alongside the automated post-restart health verification and auto-fix capabilities.

Auto-fix works during a post-restart smoke test by automatically resolving known issues found while checking gbrain and OpenClaw services. This ensures critical services return to a healthy state without requiring manual intervention after a restart.

You should run a smoke test on your gbrain environment immediately after any container restart. This verifies critical services are up, detects common post-restart issues, and applies auto-fixes to ensure environment health.

No, the smoke test skill requires no external dependencies. It operates using internal scripts to automate post-restart health checks and auto-fix known issues for gbrain and OpenClaw environments.