smoke-test-capture

Update the canonical docs/smoke-tests.md checklist for manual verification steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill smoke-test-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test-capture
Source: https://github.com/Kevin-Mok/ai-cli-dotfiles/tree/main/dot_agents/skills/smoke-test-capture
Command: npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill smoke-test-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes the repo's manual smoke coverage into a single, shared document instead of scattering checks across chats and notes.

Core Features & Use Cases

  • Centralized maintenance of smoke-test coverage.
  • Guides consistent updates to docs/smoke-tests.md when verification steps change.
  • Reduces drift by tying the smoke-test checklist to repository tasks.

Quick Start

Open docs/smoke-tests.md and update the relevant section to reflect the current verification step.

Frequently Asked Questions about smoke-test-capture

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

FAQPage Schema
How do I centralize manual smoke-test coverage in a repository?

Centralize manual smoke-test coverage by maintaining a single canonical docs/smoke-tests.md file, which consolidates scattered checks into a shared document to reduce drift and ensure consistent verification steps.

When should I update the smoke-test checklist for a task?

Update the smoke-test checklist when a task introduces a new manual verification step, changes an existing smoke-test expectation, or reveals gaps in the shared checklist to keep coverage current.

What is the best way to maintain consistency across manual verification steps?

Maintain consistency by tying the smoke-test checklist directly to repository tasks and applying prescribed format updates to the docs/smoke-tests.md sections whenever verification steps change.

How do I prevent drift in manual smoke-test documentation?

Prevent drift in manual smoke-test documentation by replacing scattered chats and notes with a single shared document, ensuring all verification steps are centralized and updated consistently.

Can I use this approach to guide updates when verification steps change?

Yes, this approach guides consistent updates to docs/smoke-tests.md by applying prescribed formats whenever a task changes existing smoke-test expectations or introduces new verification steps.

Does this method require any specific dependencies to centralize smoke tests?

No specific dependencies are required to centralize smoke tests, as the method relies solely on maintaining a docs/smoke-tests.md file to update sections and reflect current verification steps.