skills.rest
Postergully
PostergullyCOMMUNITY
Explore all skills by this author →
GitHub

smoke-test

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

Updated May 4, 2026
Search Tags:#automation#restart#health-check#smoke-test#openclaw#gbrain
One-click install
npx skills add https://github.com/Postergully/11mirror-plugin --skill smoke-test-postergully
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/Postergully/11mirror-plugin/tree/main/skills/smoke-test
Command: npx skills add https://github.com/Postergully/11mirror-plugin --skill smoke-test-postergully

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-restart health verification for gbrain and OpenClaw environments, automatically fixing known issues and surfacing failures for remediation.

Core Features & Use Cases

  • Post-restart health checks for gbrain and OpenClaw.
  • Auto-fix known issues where possible and log results for auditing.
  • Extendable with user-defined tests in ~/.gbrain/smoke-tests.d/*.sh.

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 run a post-restart health check for gbrain and OpenClaw environments?▼

Run a post-restart health check by executing the gbrain smoke-test command or bash scripts/smoke-test.sh after any container restart. This verifies gbrain and OpenClaw environments, auto-fixes known issues, and logs results to /tmp/gbrain-smoke-test.log.

Can I add my own custom tests to the smoke-test automation?▼

Yes, you can add custom tests by placing user-supplied shell scripts into the ~/.gbrain/smoke-tests.d/*.sh directory. The smoke-test automation will automatically execute these drop-in tests alongside its default gbrain and OpenClaw checks.

What does the smoke-test do when it detects a known issue?▼

When the smoke-test detects a known issue, it automatically applies auto-fixes where possible. If the failure remains unfixed, it enforces specific exit codes to surface the failure for manual remediation.

Why do I need a health check after a container restart?▼

You need a post-restart health check to verify that gbrain and OpenClaw environments have fully recovered. The smoke-test automatically identifies verification failures, auto-fixes known issues, and logs results for auditing.

Where are the smoke-test execution results logged?▼

The smoke-test execution results are logged to the /tmp/gbrain-smoke-test.log file. This log records all outcomes from the gbrain and OpenClaw health checks, including auto-fixes applied and unfixed failures.

Related Skills

Explore More Software Engineering Skills→
ltdrewltdrew
1

smoke-test

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

Community
Intermediate
Morris-UTRUSTMorris-UTRUST

smoke-test

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

Community
Advanced
yunusgungoryunusgungor

smoke-test

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

Community
Intermediate
jm199seojm199seo

canary

Monitor live pages for errors and performance regressions after deploys.

Community
Advanced