smoke
SolidBoots the local stack the way a first-time user meets it — build the binary, demo, init on a throwaway store, doctor --strict, dashboard, evidence on this repo, and the team server round trip — and reports what a reader sees. Use "does it still run", "smoke test", "first-run path", "try the binary", after any CLI or ingest change.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- assaio
- Repository
- assaio/assaio
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked to run smoke tests, validate an end-to-end user journey, dogfood a product, test a release candidate, or execute a non-deterministic workflow that may include authentication or human checkpoints. Do not use as a substitute for deterministic unit, integration, or scenario tests.
smoke-test
Fast critical-path sanity check: app boots, core path works, key endpoint responds. Run after integrating a change and again after deploy or merge, not as a full user journey. Use for smoke test, sanity check, critical path verification, does it still work, or a post-deploy check.
ui-check
Checks the offline dashboard and the site in a real browser through the browser agent — every section rendered, empty and unmeasured states as dashes, zero console and network activity, 400 px, keyboard, both themes — with screenshots kept as evidence outside the main context. Use after any dashboard, i18n, validator-text or site change, "check the dashboard", "look at the page".