unity-idm/unity / .agents/skills/update-dependencies
update-dependencies
VerifiedUpdate Maven dependency and build-plugin versions in the Unity root POM, either as one bulk patch/revision update or as an interactive full update with per-library minor/major choices, including staged Vaadin upgrades with release-note-driven compatibility work. Use when asked to discover, apply, build, and commit dependency updates in a Unity checkout.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| agents/openai.yaml | config | 213 B |
| references/dependency-policy.md | markdown | 854 B |
| references/full-mode.md | markdown | 3.1 KB |
| references/patch-mode.md | markdown | 2.9 KB |
| references/vaadin-updates.md | markdown | 6.3 KB |
| scripts/maven_metadata_candidates.pyexecutable | script | 4.6 KB |
references/dependency-policy.md
View on GitHub# Dependency policy
This policy affects only minor and major updates in full mode. Patch/revision updates remain eligible for bulk
processing.
## Manual-only non-patch updates
### Vaadin platform
- Match selectors: `vaadin.version`, `com.vaadin:vaadin-bom`, and `com.vaadin:vaadin-maven-plugin`.
- Policy: report available minor/major releases, leave them unchanged, and handle them with the dedicated staged
workflow in [vaadin-updates.md](vaadin-updates.md). Do not offer a Vaadin minor or major update as an automatic
full-mode choice.
Match primarily by the controlling version property, then by Maven coordinates. A dependency merely used by a
Vaadin module is not blacklisted unless it matches a selector above.
Keep this table narrow. Add another dependency only when the user identifies it as requiring dedicated manual
migration work.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |