upgrade-deps

Automate batched dependency upgrades with quality gates and REPORT.md generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wendeus0/AI-dotfiles --skill upgrade-deps-wendeus0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-deps
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/upgrade-deps
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill upgrade-deps-wendeus0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate safe, batched dependency upgrades across a codebase to maintain baseline integrity and reduce risk.

Core Features & Use Cases

  • Batch upgrade planning: integrates deps-health results to generate upgrade plans and apply them in small, auditable batches.
  • Quality-gate and security checks: enforces quality gates between batches and requires a security-review after relevant changes.
  • Audit-friendly workflow: covers reporting (REPORT.md) and alignment with git-flow steps (branch-sync-guard, feature-scope-guard, enforce-workflow, git-flow-manager).

Quick Start

Run upgrade-deps to begin the first upgrade batch once deps-health results are ready.

Frequently Asked Questions about upgrade-deps

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

FAQPage Schema
How do I safely batch upgrade project dependencies without breaking the baseline?

Safe batch upgrades apply dependency changes in small, auditable batches enforced by quality gates. This approach maintains baseline integrity by catching regressions between batches before proceeding to the next upgrade cycle.

What is the best way to automate dependency upgrades across multiple repositories?

Automating dependency upgrades across multi-repo ecosystems requires a batched deployment workflow. It applies an upgrade-plan gating mechanism to apply changes incrementally, ensuring ongoing maintenance does not destabilize the broader codebase.

How do dependency quality gates and security reviews work during an upgrade?

Quality gates validate baseline integrity between upgrade batches, while mandatory security reviews are triggered after relevant dependency changes. This gating mechanism prevents vulnerable or incompatible packages from merging into the main branch.

What is an upgrade plan gating mechanism for dependency maintenance?

Upgrade plan gating is an enforced workflow step that audits and controls dependency changes before application. It ensures small-batch upgrades are validated against quality gates and security reviews before generating a final REPORT.md for the PR workflow.

Can I integrate dependency upgrades with an existing git-flow manager workflow?

Yes, batched dependency upgrades align directly with git-flow manager steps. The workflow enforces branch-sync-guard, feature-scope-guard, and enforce-workflow protocols, ensuring dependency changes merge cleanly through standard git-flow practices.

When do I need a security review for a dependency upgrade batch?

A mandatory security review is required when relevant dependency changes introduce potential vulnerabilities. The upgrade workflow triggers this review automatically alongside quality gates to ensure baseline integrity before generating the final REPORT.md.