
Upgrade Everything
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Assess every version reference in a repo, evaluate available upgrades with repo-specific risk and reward, and present selectable upgrade options.
About
Upgrade-everything assesses every version reference in a repository, evaluates available upgrades against repo-specific risk and reward, and presents selectable upgrade options. It turns dependency maintenance into an informed, reviewable decision rather than a blind bump. Aimed at maintainers keeping projects current without breakage.
- Scans all version refs
- Risk/reward per upgrade
- Selectable options
- Dependency maintenance
Upgrade Everything by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install upgrade-everything@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Assess every version reference in a repo, evaluate available upgrades with repo-specific risk and reward, and present selectable upgrade options.
README.md
Upgrade Everything
Assess every version reference in a repository, evaluate available upgrades with repo-specific risk and reward, and present selectable upgrade options.
Type: Skill
Trigger: /upgrade-everything (also activates automatically)
Installation
See the marketplace install instructions.
What It Does
Builds a complete upgrade audit for the current repository by inventorying version references, resolving current upstream versions, and evaluating each available upgrade against repo-specific reward and risk. The result is a selectable Markdown matrix that includes every discovered upgrade candidate, including high-risk or low-value items, so the user can decide what to apply.
The skill applies only the upgrades the user explicitly selects. When applying upgrades, it preserves each ecosystem's normal update mechanism: package manager commands for manifests and lockfiles, targeted structured edits for configuration, and no hand-edited lockfiles when a package manager owns them.
Usage
/upgrade-everything
Examples
- "upgrade everything"
- "check dependency upgrades"
- "what can be upgraded in this repo?"
- "assess upgrades but do not apply anything"
See Also
- Pin Everything: harden mutable version references before or after upgrade review
- Release: update release metadata after selected upgrades land
- Lint and Fix: format and verify files after upgrades
- All plugins