The default test step executes repository code
Source references: 1The workflow requires `go test ./...`, not just static source inspection. Go tests and package initialization code run on the user's machine, which goes beyond a read-only scan when the repository is untrusted or newly obtained.
Malicious or side-effecting test code could read environment variables and local files, start processes, or transmit data when network access is available.
This is an active workflow step, not an example: the Skill requires `go test ./...`. That compiles and executes repository tests, package initialization code, and programs invoked by tests. In an untrusted repository, this could access files, credentials, or the network with the user's permissions. The user can require static-only review or testing in a credential-free sandbox with restricted filesystem and network access.
4. **Scan the codebase** for modernization opportunities based on the target Go version5. **Run `golangci-lint`** with the `modernize` linter if available, and `go test ./...` — Go 1.27+ runs the `stdversion` vet check by default, flagging APIs newer than the module's `go` directive; bump the directive or revert the suggestion, don't ignore the hit6. **Suggest improvements contextually**: