smoke-test

# Smoke Test Launch the app and hands-on verify that it works. Not unit/integration tests. ## Step 1: Determine Scope Resolve scope using the first match: 1. **User-specified** — the user says what to test. Use that. 2. **PR** — a PR URL or number is provided. Fetch the PR details (title, description, changed files, comments) and read the changed code. 3. **Conversation context** — prior conversation contains recent work (a feature, fix, or refactor). Extract what changed, where it lives, and expected behavior. 4. **App-level discovery** — fresh context with no prior work. Examine the project (entry points, routes, commands, README) to identify the app's core user-facing flows. Design tests that verify the app launches and its primary functionality works end-to-end. ## Step 2: Determine Testing Approach Always check for project-specific testing skills or MCP tools first. Use the fallbacks below when nothing project-specific is available: - **Web app** → `/agent-browser` skill if available, otherwise `claude-in-chrome` MCP - **UI/native app** → `computer-use` MCP - **CLI tool** → direct terminal execution - **Library with no entry point** → report that smoke testing is not applicable and stop ## Step 3: Plan Smoke Tests Design targeted smoke tests based on the scope. Each test should: 1. Exercise a specific flow from the determined scope 2. Verify the happy path works end-to-end 3. Check one obvious edge case if applicable Output the plan as text: ``` Smoke Test Pl...