smoke-test

Run eight core health tests on GBrain and OpenClaw after restarts, auto-fix issues, and log results.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill smoke-test-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/skills/smoke-test
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill smoke-test-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-restart environments often drifted health between restarts. This Skillpack runs a set of core tests to verify gbrain + OpenClaw health after a restart and auto-fix known issues before reporting, reducing downtime and manual triage.

Core Features & Use Cases

  • 8 core tests verify essential services (gbrain, worker, Codex, and gateway) after restart
  • Auto-fixes known issues when possible to restore healthy state
  • User-extensible via ~/.gbrain/smoke-tests.d/*.sh for custom checks
  • Results logged to /tmp/gbrain-smoke-test.log for post-run analysis
  • Exit code equals the number of unfixed failures (0 = all pass)

Quick Start

Run the smoke-test after any container restart to verify health and apply fixes.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate health checks after a container restart?

Automate post-restart health checks by running eight core tests to verify GBrain and OpenClaw services, automatically apply fixes to known issues, and log results for analysis. This reduces manual triage and downtime after environment restarts.

What is a smoke test in CI pipelines and production deployments?

A smoke test in CI pipelines verifies essential services like GBrain, worker, Codex, and gateway are operational after deployment. It runs core health checks, auto-fixes known problems, and exits with the count of unfixed failures to signal pipeline status.

Can I add custom health checks for GBrain and OpenClaw?

Add custom health checks by placing executable shell scripts in the ~/.gbrain/smoke-tests.d directory. These user-provided tests run alongside the eight core tests to verify environment-specific requirements after a container restart.

How do I verify OpenClaw gateway health and apply automatic fixes?

Verify OpenClaw gateway health by executing the smoke-test scripts which detect service issues and auto-fix known failures. Results are logged to /tmp/gbrain-smoke-test.log, and the exit code reflects the number of unresolved failures.

Why does my production deployment fail after restart without manual triage?

Production deployments fail after restart due to environment drift between restarts. Running automated smoke tests detects these health issues, applies auto-fixes, and logs results to prevent manual triage and reduce downtime.