go

Original：🇺🇸 English

Translated

Finish the current work Boris-style. Test it end-to-end, simplify the diff, then open a PR and stop. The PR's CI gate and the reviewer own everything after that. Use when the user says "/go", "go", or ends a request with "then go".

18installs

Sourcedividendsolo/skills

Added on2026-07-07

NPX Install

npx skill4agent add dividendsolo/skills go

SKILL.md Content

View Translation Comparison →

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
```
related
```
on 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.

2. Simplify

Make one reduction pass over the full diff before it ships: delete anything that does not earn its place (single-caller abstractions, unused branches, speculative handling, leftovers from abandoned approaches). Behavior must not change. Use the code-simplifier agent for a large diff; do it inline for a small one. Re-run the step 1 tests if the pass changed code. If nothing comes out, say so and move on.

3. Open a PR

Branch from the current work (
```
feature/<slug>
```
or
```
bug/<slug>
```
; include the ticket identifier if there is one), commit, push.
```
gh pr create
```
with a body that says what changed and how it was verified; "Closes <ID>" when a ticket exists.
Stop. Never merge your own PR; CI gates it and the reviewer merges or kicks it back. If the card exists on a board, move it to In Review.

go

NPX Install

Tags

SKILL.md Content

Go

1. Test end-to-end

2. Simplify

3. Open a PR