skills.rest
weiping
weipingCOMMUNITY
Explore all skills by this author →
GitHub

smoke-test

Verify GBrain and OpenClaw environments after container restarts with health checks and repairs.

1|Updated May 9, 2026
Search Tags:#auto-fix#health check#OpenClaw#smoke testing#database connectivity#container restart#GBrain CLI
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill smoke-test-weiping
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/weiping/gbrain-cn/tree/main/skills/smoke-test
Command: npx skills add https://github.com/weiping/gbrain-cn --skill smoke-test-weiping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Smoke tests prevent production downtime and broken agent behavior by catching failed services right after a restart and automatically repairing known, repeatable issues before reporting.

Core Features & Use Cases

  • Post-restart health verification: Runs 8 core checks to confirm GBrain and OpenClaw readiness (CLI loads, workers connect, Codex plugin works, DB diagnosis passes).
  • Known failure auto-fix: Applies targeted, idempotent repairs (e.g., reinstalls a missing Zod core module) when a check fails, then re-tests to confirm the fix.
  • Extensible drop-in tests: Allows users to add fast custom checks via ~/.gbrain/smoke-tests.d/*.sh to cover environment-specific needs.
  • Actionable logging and exit code: Writes a structured run log to /tmp/gbrain-smoke-test.log and returns an exit code equal to the number of unfixed failures.

Quick Start

Run gbrain smoke-test after any container restart to validate and repair critical services.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I run smoke tests to verify GBrain and OpenClaw services after a container restart?▼

Run gbrain smoke-test after any restart to validate services. It executes 8 core health checks covering CLI loads, worker connections, Codex plugin functionality, and database connectivity diagnosis to confirm environment readiness.

Can smoke testing automatically fix common database connectivity or module breaks after a restart?▼

Yes, smoke testing applies targeted idempotent auto-fixes for known failures, such as reinstalling a missing Zod core module, then re-tests to confirm the repair before logging the final result.

How do I add custom health checks to my smoke testing suite for environment-specific validation?▼

You can extend the suite by dropping fast custom executable test scripts into ~/.gbrain/smoke-tests.d/*.sh, which run alongside the 8 core checks to cover your specific environment needs.

What does the smoke test exit code indicate about unfixed service failures?▼

The exit code equals the number of unfixed failures remaining after the run. A zero exit code means all health checks passed or were successfully repaired, while a non-zero count indicates unresolved issues.

Where are smoke test results and health check logs stored for incident triage?▼

Structured run logs are written to /tmp/gbrain-smoke-test.log, providing actionable records of passed checks, applied auto-fixes, and remaining failures for post-restart incident triage workflows.

Related Skills

Explore More Software Engineering Skills→
NinatuziNinatuzi

smoke-test

Run diagnostic tests and apply self-healing fixes for gbrain and OpenClaw environments.

Community
Advanced
PostergullyPostergully

smoke-test

Verify post-restart health of gbrain and OpenClaw environments with drop-in tests.

Community
Advanced
inbrainfuninbrainfun
174

smoke-test

Runs smoke tests for Inbrain and OpenClaw after restart, applying auto-fixes and logging to /tmp/inbrain-smoke-test.log.

Community
Advanced
pacphipacphi
14

Docker Manager

Manage the VisionFlow container lifecycle and execute in-container commands via Docker socket.

Community
Advanced