smoke-test

Automate post-restart smoke tests and auto-fix known issues in gbrain and OpenClaw environments.

2|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/bish-x/bx-gbrain --skill smoke-test-bish-x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/bish-x/bx-gbrain/tree/main/skills/smoke-test
Command: npx skills add https://github.com/bish-x/bx-gbrain --skill smoke-test-bish-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates post-restart smoke tests and auto-fixes known issues for gbrain and OpenClaw environments, ensuring system health and reliability.

Core Features & Use Cases

  • Automated Smoke Tests: Runs critical tests after a container restart to verify system functionality.
  • Auto-Fix Known Issues: Automatically resolves common issues identified during the smoke tests.
  • Extensible via User Scripts: Allows users to add custom tests for specific needs.

Quick Start

Run the smoke test command after any container restart with gbrain smoke-test.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate smoke testing for gbrain and OpenClaw environments after a restart?▼

To automate smoke testing after a restart, run the `gbrain smoke-test` command to verify system functionality and automatically apply fixes for known issues in gbrain and OpenClaw environments.

What is the best way to auto-fix known issues in OpenClaw post-restart?▼

The best way to auto-fix known issues in OpenClaw post-restart is using automated smoke tests that perform critical system checks and apply automatic resolutions for identified problems.

Can I add custom smoke tests for specific system health checks in gbrain?▼

Yes, you can add custom smoke tests for specific system health checks in gbrain by extending the Skill with your own user scripts to meet specialized testing requirements.

Do I need access to gbrain and OpenClaw environments to run automated smoke tests?▼

Yes, you need direct access to gbrain and OpenClaw environments and the ability to execute scripts to run automated smoke tests and apply post-restart fixes.

Why does my system health check fail after a container restart?▼

System health checks fail after a container restart due to known issues that require critical system verification, which automated smoke tests can detect and auto-fix.