Skip to content

opensite-ai/opensite-skills / dependency-upgrade-orchestrator

dependency-upgrade-orchestrator

Verified

Language- and framework-agnostic process for upgrading one or more dependencies safely and systematically. Resolves version and peer conflicts before touching code, uses search tools to read changelogs and migration guides to find the exact breaking changes between the installed and target versions, applies every required code change, and verifies with the project's own build, lint, and test gates. Use when asked to bump, upgrade, or update a package (or a batch of packages), migrate a major version, handle breaking changes from a dependency, or modernize a lockfile across any ecosystem (Cargo, npm/pnpm/yarn, pip/Poetry/uv, Go modules, Maven/Gradle, Bundler, Composer, and others).

FileKindSize
SKILL.mdskill md13.4 KB
agents/openai.yamlconfig421 B
examples/js-major-upgrade.mdmarkdown2.6 KB
examples/rust-multi-upgrade.mdmarkdown4.9 KB
references/activation.mdmarkdown1.7 KB
templates/changelog-diff.mdmarkdown1.2 KB
templates/upgrade-plan.mdmarkdown970 B

templates/upgrade-plan.md

View on GitHub
# Upgrade Plan

> Fill this in during Phase 0–1. One row per dependency, including any
> transitive major bumps discovered in Phase 1.

## Context
- **Repo / package:**
- **Ecosystem / package manager:**
- **Baseline status (build / lint / test):** ⬜ green  ⬜ red — _must be green before starting_
- **Canonical commands** (from repo scripts / CI):
  - build: `...`
  - lint: `...`
  - test: `...`

## Dependencies

| Dependency | From (lockfile) | Target | Direct/Transitive | Risk (patch/minor/major) | Sequence | Notes |
|------------|-----------------|--------|-------------------|--------------------------|----------|-------|
| `example-pkg` | 1.2.7 | 1.4.0 | direct | minor | 1 | |
| | | | | | | |

## Conflicts Found (Phase 1)
- _None_ — or list each constraint chain: `pkg-a@X requires pkg-b <Y`, resolution: ...

## Upgrade Order
1.
2.

## Adopt-New-Functionality (only if user requested)
- ⬜ Not requested — keep diff minimal
- Requested items:
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall