skills.rest
gtapps
gtappsCOMMUNITY
Explore all skills by this author →
GitHub

smoke-test

Validate post-hatch Hermit configuration and runtime setup with a PASS/WARN/FAIL report.

69|12|Updated Mar 23, 2026
Search Tags:#validation#config#diagnostics#smoke-test#routines#post-hatch#OPERATOR.md
One-click install
npx skills add https://github.com/gtapps/claude-code-hermit --skill smoke-test-gtapps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/gtapps/claude-code-hermit/tree/main/plugins/claude-code-hermit/skills/smoke-test
Command: npx skills add https://github.com/gtapps/claude-code-hermit --skill smoke-test-gtapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-hatch validation automates the verification of the Hermit setup, ensuring essential files and configurations are correct before use.

Core Features & Use Cases

  • Config validation: checks presence and validity of config.json and plugin version alignment.
  • OPERATOR.md sanity: ensures OPERATOR.md exists and contains meaningful content for project context.
  • Routine and scheduled check validation: validates configured routines and loaded skills, producing a concise report.
  • Channel and state checks: optionally verifies channel readiness and state file integrity to catch misconfigurations early.

Quick Start

After hatch, trigger the smoke test to automatically produce a report detailing PASS/WARN/FAIL statuses and remediation guidance.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I validate post-hatch configuration files for runtime issues?▼

Post-hatch validation checks config.json and OPERATOR.md to surface configuration and runtime issues, verifying essential files and producing a PASS/WARN/FAIL report with remediation guidance.

What is the best way to automate setup verification after a project hatch?▼

Automated setup verification applies after hatch to check config.json validity, OPERATOR.md sanity, scheduled checks, and routine references, generating a concise report detailing project readiness.

How do I check if my scheduled routines and loaded skills are configured correctly?▼

Routine validation verifies configured routines and loaded skills within the harness, checking routine references across the project to catch misconfigurations and ensure plugin state integrity.

Does post-hatch validation require access to specific plugin state files?▼

Yes, post-hatch validation requires access to .claude-code-hermit/config.json, .claude-code-hermit/OPERATOR.md, the loaded skills harness, and plugin state to perform checks and generate remediation guidance.

Can I verify channel readiness and state file integrity during a smoke test?▼

Channel and state checks optionally verify channel readiness and state file integrity during the smoke test, catching misconfigurations early before the project setup is used.

Why does my config.json validation fail after hatch?▼

Config validation fails when config.json is missing, invalid, or has plugin version misalignment, producing a FAIL status in the report with specific remediation guidance to fix the configuration.

Related Skills

Explore More Software Engineering Skills→
gtappsgtapps
69

dev-doctor

Inspect claude-code-hermit setups for misconfigurations and safety issues.

Community
Advanced
Patasse97Patasse97

skill-security-auditor

Audit AI agent skills for security and generate a verdict report.

Community
Advanced
gtappsgtapps
69

hatch

Append a dev workflow to CLAUDE.md and configure git safety.

Community
Advanced
LayerDynamicsLayerDynamics

audit

Audit project dependencies and configurations for vulnerabilities, secrets, and unsafe settings.

Community
Advanced