smoke-test

Automate post-restart health checks and auto-fix routines for gbrain and OpenClaw.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-restart health verification for gbrain and OpenClaw environments, with auto-fix routines to recover from common restart issues.

Core Features & Use Cases

  • 8 core tests verify health after restart
  • Auto-fixes known issues before reporting
  • Extensible via drop-in scripts in ~/.gbrain/smoke-tests.d/*.sh
  • Logs results to /tmp/gbrain-smoke-test.log
  • Exit code equals number of unfixed failures (0 = all pass)

Quick Start

Run gbrain smoke-test or bash scripts/smoke-test.sh after any container restart.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate post-restart health checks for containerized gbrain deployments?

You can extend smoke checks by placing custom shell scripts in the ~/.gbrain/smoke-tests.d/*.sh directory. The system runs these pluggable extensions alongside its 8 built-in tests during the post-restart verification process.

What does the exit code mean when running a container smoke test?

Yes, the smoke test includes auto-fix routines that automatically resolve common restart issues for gbrain and OpenClaw before reporting. Any remaining unfixed failures are counted and reflected in the final exit code.

Do I need any specific dependencies to run OpenClaw health verification scripts?

After completing the smoke test, review the logged results in /tmp/gbrain-smoke-test.log to analyze failures. Use the exit code to gate workload startup or trigger alerting workflows in your containerized automation pipeline.

complementary

Integrate container orchestration scheduling tools to trigger smoke-test execution automatically on restart, verifying gbrain workload readiness and gating deployment progression based on exit codes.