go-deps-security-upgrade

Automate grouped Go dependency security upgrades with one commit per logical group.

8.9k|794|Updated Aug 19, 2016
One-click install
npx skills add https://github.com/fission/fission --skill go-deps-security-upgrade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go-deps-security-upgrade
Source: https://github.com/fission/fission/tree/main/.claude/skills/go-deps-security-upgrade
Command: npx skills add https://github.com/fission/fission --skill go-deps-security-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a grouped, bisectable Go dependency security sweep on the Fission repo. Use when the user asks to upgrade outdated/vulnerable Go dependencies, run a dep security pass, or process CVE findings from govulncheck. Produces one commit per logical dependency group on a dedicated branch so failures are attributable and revertable.

Core Features & Use Cases

  • Baseline security scan with govulncheck to identify vulnerabilities in Go dependencies.
  • Grouped upgrades: upgrade related dependencies in logically separable commits on dedicated branches for traceability.
  • Reproducible workflow: each commit corresponds to a specific vulnerability group, enabling precise bisecting and rollback.

Quick Start

Run the baseline govulncheck, then start the grouped Go dependency upgrade workflow on your repository.

Frequently Asked Questions about go-deps-security-upgrade

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

FAQPage Schema
How do I upgrade vulnerable Go dependencies identified by govulncheck?▼

You can upgrade vulnerable Go dependencies by running a baseline govulncheck scan, grouping related dependency upgrades logically, and producing one traceable commit per group on a dedicated branch to isolate CVE remediation.

What is the best way to group Go dependency security upgrades for safe rollback?▼

Grouping Go dependency upgrades involves applying related updates in logically separable commits on a dedicated branch, ensuring each commit corresponds to a specific vulnerability group for precise bisecting and easy rollback.

How does a bisectable Go dependency sweep work for CVE remediation?▼

A bisectable Go dependency sweep works by running a baseline security scan, grouping upgrades, running go mod tidy and builds, and yielding traceable commits on a dedicated branch for each group to isolate failures.

Can I process govulncheck findings by upgrading one logical dependency group at a time?▼

Yes, you can process govulncheck findings by automating a grouped dependency security sweep that upgrades related dependencies in logically separable commits, making failures attributable and revertable.

Why should I use grouped commits instead of a single commit for Go security upgrades?▼

Grouped commits isolate each logical dependency upgrade on a dedicated branch so that build failures are attributable to specific vulnerability groups and can be reverted without rolling back the entire security sweep.