name	verify
description	Verify a code change does what it should by running the app. Use this when reviewing a PR, after making a feature change, or when asked to "check if it works", "test the change", "verify the fix", "make sure nothing broke", or "validate the implementation". Also trigger when the user mentions smoke testing, end-to-end verification, manual testing, or running the app to confirm behavior.

Verify a Code Change

Confirm the change does what it should — and doesn't break existing behavior.

Understand the change — check the diff or recent commits to know what was modified
Build/lint — ensure the project compiles and passes any lint/type checks
Run tests — execute existing test suites; add new tests if none exist for the changed area
Manual smoke test — start the app and exercise the changed path end-to-end
Edge cases — think about boundary conditions, error paths, and regression scenarios
Report — summarize what you tested, what passed, and what failed (with specifics)

name	verify
description	Verify a code change does what it should by running the app. Use this when reviewing a PR, after making a feature change, or when asked to "check if it works", "test the change", "verify the fix", "make sure nothing broke", or "validate the implementation". Also trigger when the user mentions smoke testing, end-to-end verification, manual testing, or running the app to confirm behavior.

Confirm the change does what it should — and doesn't break existing behavior.

Understand the change — check the diff or recent commits to know what was modified
Build/lint — ensure the project compiles and passes any lint/type checks
Run tests — execute existing test suites; add new tests if none exist for the changed area
Manual smoke test — start the app and exercise the changed path end-to-end
Edge cases — think about boundary conditions, error paths, and regression scenarios
Report — summarize what you tested, what passed, and what failed (with specifics)

verify