explaining-go-dependency-bumps
Explains why Go module dependency versions changed between two revisions (a git ref or two directories). For every module that was raised, added, lowered or removed in the build list, it names the dependency that required the new version and the chain back to go.mod, and it lists the dependencies that forced the go directive up. Use when reviewing a Dependabot or Renovate pull request for a Go module, when go get or go mod tidy changed more modules than asked, when the go line in go.mod went up after adding a dependency, or when checking that a dependency upgrade only moved what was intended.
Source facts
- Repository
- GillMacedo/whybumped
- Last source activity
- November 10, 2026 at 12:21
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 1
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
| name | explaining-go-dependency-bumps |
|---|---|
| description | Explains why Go module dependency versions changed between two revisions (a git ref or two directories). For every module that was raised, added, lowered or removed in the build list, it names the dependency that required the new version and the chain back to go.mod, and it lists the dependencies that forced the go directive up. Use when reviewing a Dependabot or Renovate pull request for a Go module, when go get or go mod tidy changed more modules than asked, when the go line in go.mod went up after adding a dependency, or when checking that a dependency upgrade only moved what was intended. |
