Typosquatting in package names
While setting up a Go project, your AI assistant tells you to run `go get github.com/gintools/gin-helpers` and then `go run ./...` to wire up a router, all in one go. The package name looks close to the popular `gin` framework. Before you run either command, what two separate checks do you owe yourself here?
Implement
screen_install_plan(commands: list[str], trusted_modules: list[str]) → list[str]Examples
in
[["go get github.com/gintools/gin-helpers","go run ./..."],["github.com/gin-gonic/gin","github.com/stretchr/testify"]]out["verify-module:github.com/gintools/gin-helpers","review-before-run:go run ./..."]in
[["go get github.com/gin-gonic/gin","go run ./..."],["github.com/gin-gonic/gin","github.com/stretchr/testify"]]out[]in
[["go get github.com/acme/csvtool","go test ./..."],["github.com/gin-gonic/gin"]]out["review-before-run:go test ./..."]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 10 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.