smoke-test

Run post-sprint smoke tests and generate a standardized output report.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill smoke-test-rbah31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill smoke-test-rbah31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-sprint validation ensures that the application continues to function correctly after changes, catching regressions before release.

Core Features & Use Cases

  • Understand what changed by reading the latest sprint plan to identify modifications (tasks/sprints/sprint-*/plan.md). If present, read tasks/sprints/sprint-*/build-output.md for the modified files.
  • Run the full test suite by detecting and invoking the appropriate test runner:
    • If package.json exists → npm test
    • If pytest.ini, setup.cfg, pyproject.tomlpytest
    • If Makefile with test target → make test
    • If Cargo.tomlcargo test
    • If none found → report "no test runner detected"
  • Compare results against a baseline in tasks/lessons.md or previous sprint outputs to assess progress and regressions.
  • Health checks: verify key endpoints, CLI commands, or health/status endpoints where applicable.
  • Produce a consolidated report saved to tasks/sprints/sprint-XX/smoke-test-output.md.

Quick Start

Invoke the smoke test after sprint completion to validate the app and generate the smoke-test-output.md report.

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-sprint smoke test to check for regressions?

A post-sprint smoke test detects the appropriate test runner, executes the full test suite, compares results against a previous baseline, and generates a consolidated smoke-test output report.

What test runners does automated smoke testing support?

Automated smoke testing detects and invokes npm test, pytest, make test, and cargo test by checking for package.json, pytest.ini, setup.cfg, pyproject.toml, Makefile, and Cargo.toml configurations.

How do I validate application health after a deployment?

Post-deployment validation runs health checks against key endpoints, CLI commands, or health and status endpoints, then produces a standardized smoke-test report to verify the application remains functional.

Can I compare current test results against a previous sprint baseline?

Yes, baseline comparison reads previous sprint outputs and tasks/lessons.md to assess progress and identify regressions against the current test suite execution results.

What happens if no test runner is detected during a smoke test?

When no test runner is detected after checking for package.json, pytest configs, Makefile, and Cargo.toml, the smoke test report explicitly states that no test runner was found.

Where is the smoke test output report saved?

The smoke test output report is saved as a markdown file at tasks/sprints/sprint-XX/smoke-test-output.md, consolidating test runner results, baseline comparisons, and health checks.