smoke-test

Run automated smoke tests validating gbrain and OpenClaw health after restarts.

Updated May 16, 2026

Search Tags:#automation #reliability #health-check #smoke-test #openclaw #gbrain #custom-tests

Ready to run

npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill smoke-test-morris-utrust

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/skills/smoke-test
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill smoke-test-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-restart smoke tests verify gbrain and OpenClaw health, automatically detecting and fixing common issues to keep services online without manual intervention.

Core Features & Use Cases

Runs eight core health checks after container restarts and reports results.
Auto-fixes known issues and allows user-defined tests via ~/.gbrain/smoke-tests.d/*.sh.
Logs results to /tmp/gbrain-smoke-test.log and surfaces exit status as the count of unfixed failures for integration into CI and restart workflows.

Quick Start

Run gbrain smoke-test after any container restart to verify health and auto-fix issues.

Frequently Asked Questions about smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run automated smoke tests to validate gbrain and OpenClaw health after a container restart?▼

Run automated smoke tests after container restarts to validate gbrain and OpenClaw health. The Skill coordinates eight core checks, auto-fixes known issues, and logs results to /tmp/gbrain-smoke-test.log for verification.

Can I add custom health checks to verify gbrain and OpenClaw services?▼

Yes, you can add custom health checks by placing user-defined test scripts under ~/.gbrain/smoke-tests.d/*.sh. These scripts extend the eight core smoke tests to cover additional service validation scenarios.

What is the best way to integrate post-restart health checks into a CI pipeline?▼

Integrate post-restart health checks into CI pipelines by running the smoke test and checking its exit status. The exit code equals the number of unfixed failures, enabling automated pass/fail decisions in restart workflows.

Does the smoke test auto-fix known issues or just report service health errors?▼

The smoke test auto-fixes known issues detected during health checks, not just reporting errors. It attempts automatic remediation for common gbrain and OpenClaw problems before surfacing any remaining unfixed failures.

Why does my gbrain smoke test exit with a non-zero code after a restart?▼

A non-zero exit code indicates unfixed failures from the smoke test. The exit status represents the exact count of health checks that failed and could not be auto-fixed, signaling issues requiring manual intervention.

Do I need any dependencies to run OpenClaw and gbrain post-restart health checks?▼

No external dependencies are required to run post-restart health checks. The Skill relies only on its internal scripts to execute the eight core smoke tests and any custom scripts placed in the smoke-tests.d directory.