What problem does it solve? Go projects accumulate dependencies that need safe upgrading, vulnerability auditing, and conflict resolution, and mistakes like gitignoring go.sum or blindly running go get -u introduce supply-chain and stability risks. ## Core Features & Use Cases - Safe Dependency Lifecycle: Add, upgrade (patch-first), and remove Go modules with go.mod/go.sum hygiene rules, including Go 1.24+ tool directives for pinning CLI tools like golangci-lint and govulncheck. - Auditing & Visualization: Scan for reachable vulnerabilities with govulncheck, track outdated modules with go-mod-outdated, and analyze binary size contributions with goweight or go-size-analyzer. - Conflict Resolution & Workspaces: Diagnose version conflicts with go mod graph, apply replace/exclude/retract directives correctly, and manage multi-module development with go.work files. - Use Case: Before a release, run govulncheck ./... to catch CVEs in called code paths, upgrade with go get -u=patch ./..., tidy the module, and verify tests pass. ## Quick Start Ask the agent to audit your Go project's dependencies for vulnerabilities and outdated packages, then propose a safe patch-level upgrade plan.