Skip to content

j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/addons/dependency-upgrade

deepworkplan-addon-dependency-upgrade

Verified

DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Near-default — offered for every repo with declared dependencies, and its delegator installs under the onboarding consent unless declined; upgrades themselves never run automatically, only as explicit, gated work. Never required for baseline conformance; reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build.

FileKindSize
SKILL.mdskill md10.4 KB
SPEC.mdmarkdown8.5 KB
addon.jsonconfig221 B
templates/ecosystems.mdmarkdown5.8 KB
templates/lib-upgrade-command.mdmarkdown2.0 KB
templates/upgrade-report.mdmarkdown1.4 KB

templates/upgrade-report.md

View on GitHub
# Template — Dependency Upgrade Report (reasoning aid)

This is the **report shape** to produce after the upgrade flow. Fill it by
reasoning about what actually happened; keep the sections, drop rows that do not
apply. Do **not** auto-commit — surface this report and the diff, and let the
developer commit.

```markdown
# Dependency Upgrade Report

**Date:** <YYYY-MM-DD>
**Ecosystem(s):** <e.g. JS/TS (pnpm), Python (poetry)>
**Package manager(s) detected from:** <manifest + lockfile that decided it>

## Summary

- Upgraded: <N> dependencies across <M> batches
- Skipped / reverted: <N> (see below)
- Majors: <approved N / deferred N>

## Upgraded (by tier)

### Patch
- <pkg>: <old> → <new>

### Minor
- <pkg>: <old> → <new>

### Major (developer-approved)
- <pkg>: <old> → <new>

## Skipped / Reverted

- <pkg>: <old> → <new> — **reverted**; gate failed: `<command>` (<reason>)
- <pkg>: <old> → <new> — **deferred** (major, awaiting review)

## Validation

- Gate used (the repo's real commands): `<command set>`
- Result per accepted batch: ✅ pass

## Files changed

- <manifest> (e.g. package.json / pyproject.toml / Cargo.toml / go.mod)
- <lockfile> (e.g. pnpm-lock.yaml / poetry.lock / Cargo.lock / go.sum)

## Recommended follow-ups

- <e.g. revisit the deferred major once upstream X lands>
- Suggested commit: `chore(deps): upgrade <N> dependencies (patch + minor)`
```
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall