smoke-test

Automate end-to-end smoke testing of the dev-process-toolkit plugin against a fresh Bun project.

6|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/nesquikm/dev-process-toolkit --skill smoke-test-nesquikm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill smoke-test-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates an end-to-end smoke-test flow for the dev-process-toolkit plugin against a fresh Bun project, coordinating separate Linear and Jira tracker paths and producing per-run artifacts for pre-release sanity checks.

Core Features & Use Cases

  • Orchestrates a canonical six-phase workflow: setup, spec-write, implement, gate-check, spec-review, and simplify.
  • Supports two trackers (linear and jira) with per-tracker MCP configs and isolated run artifacts.
  • Generates and verifies per-run artifacts, MCP configuration, and teardown procedures to ensure repeatable pre-release checks.

Quick Start

Run /smoke-test --tracker linear to perform a complete end-to-end smoke test against a fresh Bun project.

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 smoke tests for a dev-process-toolkit plugin against a fresh Bun project?

End-to-end plugin smoke tests validate the entire dev-process-toolkit skill chain from /setup through /simplify by running a six-phase workflow against a fresh Bun project to ensure reliable pre-release verification.

How do I run a smoke test using the Linear tracker integration?

To run a Linear tracker smoke test, execute the /smoke-test command with the --tracker linear flag to initiate environment preparation and generate isolated per-run artifacts for pre-release sanity checks.

Does the smoke test workflow support both Linear and Jira MCP configurations simultaneously?

The smoke test workflow supports both Linear and Jira trackers by applying per-tracker MCP configs and maintaining isolated run artifacts for each path during the end-to-end plugin verification.

What is included in the six-phase dev-process-toolkit smoke test workflow?

The six-phase dev-process-toolkit smoke test workflow includes setup, spec-write, implement, gate-check, spec-review, and simplify phases to validate the entire skill chain from start to finish.

Can I use this smoke test approach for pre-release sanity checks before shipping milestones?

You can use this smoke test approach for pre-release sanity checks prior to ship milestones, as it specifically validates the entire skill chain and generates per-run artifacts to ensure reliable verification.

What teardown and artifact verification procedures are generated during the plugin smoke test?

The plugin smoke test generates and verifies per-run artifacts, MCP configuration, and teardown procedures to ensure repeatable pre-release checks across isolated Linear and Jira tracker paths.