One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill upgrade-deps-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-deps
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/upgrade-deps
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill upgrade-deps-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents risky, messy dependency upgrades by organizing updates into security, safe versioning, and explicitly-gated major upgrades, with tests between each tier so regressions are isolated and easy to revert.

Core Features & Use Cases

  • Risk-tiered upgrade batches: groups upgrades into ADVISORY, PATCH+MINOR, and per-package MAJOR to match rollback granularity to change risk.
  • Advisory-aware selection: checks both current and target versions for advisories and avoids landing a target that is still vulnerable.
  • Workflow guardrails: runs the project’s discovered test/build command between groups and halts on failures instead of fixing forward.
  • Monorepo-aware execution: detects workspace/monorepo roots and asks whether to upgrade root-only or a specific workspace before proceeding.

Quick Start

Tell the AI: Upgrade dependencies for a release by detecting the lockfile(s), auditing outdated and advisory risks, and applying only the approved batches with tests between each phase.

Frequently Asked Questions about upgrade-deps

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

FAQPage Schema
How do I safely upgrade dependencies and avoid breaking my release workflow?

Safe dependency upgrades require batching changes into risk tiers, running tests between each batch, and preserving clean rollback granularity so regressions are isolated and easy to revert.

What is the best way to handle semantic versioning updates without introducing vulnerabilities?

Semantic versioning updates should be checked using advisory-aware selection that audits both current and target versions, ensuring the target version is not still vulnerable before applying the upgrade.

How do I batch package audit results for a release pre-step?

Package audit results are grouped into ADVISORY, PATCH+MINOR, and per-package MAJOR batches, matching rollback granularity to change risk while requiring per-major user approval.

Does this dependency management workflow support monorepo workspaces?

Monorepo workspace execution is supported by detecting workspace and monorepo roots, prompting whether to upgrade root-only or a specific workspace before proceeding with tiered upgrades.

What happens if tests fail during a dependency upgrade phase?

Test failures halt the dependency upgrade workflow immediately using stop-on-red behavior, preventing forward fixing and ensuring regressions remain isolated to the specific commit batch.

How to rollback dependency upgrades when a build breaks?

Rolling back dependency upgrades relies on tiered commit batching, where grouping changes by ADVISORY, PATCH+MINOR, and MAJOR risk tiers preserves clean Git rollback granularity for each failed group.