gh-oss-go-bump

Identify Go repositories and update them to the latest stable Go version.

15|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jackchuka/skills --skill gh-oss-go-bump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-oss-go-bump
Source: https://github.com/jackchuka/skills/tree/main/gh-oss-go-bump
Command: npx skills add https://github.com/jackchuka/skills --skill gh-oss-go-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go versions drift across multiple OSS repositories, causing inconsistency and maintenance overhead. This Skill coordinates discovery, validation, and releases-safe upgrades to keep all repos aligned.

Core Features & Use Cases

  • Discover and identify all Go repositories (via gh oss-watch) and determine the latest stable Go version.
  • Compare current repo Go versions and assess CI strategies, test coverage, and upgrade blockers.
  • Validate changes locally (go mod tidy, go test) before creating PRs, with user-controlled gates.
  • Generate PRs with clear messages and automate workflows while preserving safety and review gates.
  • Suitable for teams managing multiple Go-based OSS projects or monorepos requiring coordinated upgrades.

Quick Start

Scan your Go repositories, determine the latest stable Go version, and kick off a controlled bump workflow with explicit user confirmations.

Frequently Asked Questions about gh-oss-go-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Go version bumps across multiple GitHub repositories?

You can automate Go version bumps by discovering repositories, determining the latest stable Go version, and validating changes locally before creating PRs. This Skill assesses CI strategies and test coverage to ensure safe upgrades across all repos.

How do I update go.mod and run tests before creating a pull request?

To update go.mod safely, the workflow runs go mod tidy and go test locally to validate changes. PRs are only generated after local verification passes and you provide explicit confirmation.

What is the safest way to upgrade Go versions in OSS projects without breaking CI?

The safest way to upgrade Go versions involves assessing each repository's current configuration, CI strategy, and test coverage. This Skill evaluates potential upgrade risks and validates locally before submitting any PRs.

Can I assess upgrade risks and CI strategies for multiple Go repositories at once?

Yes, you can assess upgrade risks across multiple Go repositories simultaneously. The Skill compares current Go configurations and CI strategies to identify blockers and determine which version bumps are safe to execute.

How do I discover which of my GitHub repositories need a Go version update?

You can discover Go repositories needing updates by scanning your repositories to identify those using Go. The Skill then compares current versions against the latest stable Go version to determine which repos require a bump.

Do I need to manually review pull requests after automating Go version bumps?

Yes, manual review is required because the workflow includes user-controlled gates. PRs are only created after you confirm the local verification results, ensuring you maintain oversight of automated version upgrades.