go
Installation
SKILL.md
Go
Close out the current work in three steps, then stop. Do not run the full local validation pipeline; that is CI's job on the PR. If CI fails, the reviewer kicks it back and it comes around again.
1. Test end-to-end
Prove the change works as a user would see it, not just that units pass.
- Run the tests relevant to the change locally (Vitest
relatedon the touched files, plus any e2e spec that exercises the touched surface). They must pass. - If the change has a user-facing surface, exercise it for real: UI through the repo's browser verification rules (Chrome extension, agent browser), backend by hitting the running service. Fix what you find before moving on.