smoke-test

Automate end-to-end sanity checks using the tt-client binary.

2|Updated Sep 12, 2012
One-click install
npx skills add https://github.com/jiikko/dotfiles --skill smoke-test-jiikko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/jiikko/dotfiles/tree/main/_claude/skills/smoke-test
Command: npx skills add https://github.com/jiikko/dotfiles --skill smoke-test-jiikko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end sanity checks of the application, using the tt-client binary to quickly verify that core flows work after changes.

Core Features & Use Cases

  • End-to-end Validation: Run quick, standard, or complete test scopes to validate core features, UI interactions, and reporting scenarios.
  • Pre-checks and Reporting: Validate workspace/app state and produce a concise results summary for teams.
  • Use Case: When you deploy a new version, run a smoke test to confirm basic connectivity and primary user flows before broader testing.

Quick Start

Run the smoke test from the command line or UI:

  • /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 end-to-end sanity checks after a deployment?

Automate end-to-end sanity checks by running the smoke-test workflow, which uses the tt-client binary to validate core features, UI flows, and reporting scenarios. It executes pre-checks, subagent tasks, and consolidates results for rapid feedback.

What is the best way to run a quick smoke test on core application features?

Run a quick smoke test using the /smoke-test command to validate core features and primary user flows in minutes. This standard scope ensures basic connectivity and application stability before broader testing.

Does the smoke test support different validation scopes for UI interactions?

Yes, the smoke test supports quick, standard, and complete test scopes to validate UI interactions and reporting scenarios. You can choose the scope to match the depth of end-to-end validation needed after changes.

When do I need to run an end-to-end smoke test?

Run an end-to-end smoke test when you deploy a new version or make changes, needing to confirm basic connectivity and primary user flows. It provides a concise results summary to verify application sanity rapidly.