Skill

dep-upgrade

Upgrade de dependencias com analise de impacto. Assess, upgrade, fix, verify. Para: atualizar pacotes, bump de versoes, renovate, npm update. Ativado por: /dep-upgrade, "atualizar dependencias", "upgrade", "outdated", "bump".

Install

npx claudepluginhub souzalemos/spec-driven-workflow --plugin spec-driven-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

4 fases com artefatos em .spec/workflows/upgrades/.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Stars1

Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Dependency Upgrade — Upgrade seguro

4 fases com artefatos em .spec/workflows/upgrades/.

Fase 1: Assess

Liste dependencias desatualizadas: npm outdated / equivalente

Para cada upgrade alvo:

Leia changelog / release notes
Identifique breaking changes
Verifique migration guides
Avalie impacto no codebase (grep por APIs afetadas)

Priorize: quais agora, quais adiar

Crie .spec/workflows/upgrades/ASSESSMENT.md:

Lista com current -> target versions
Breaking changes por dependencia
Ordem de upgrade (deps antes de dependents)
Risk assessment

Gate: Confirme scope com humano

Fase 2: Upgrade

Upgrade UMA dependencia (ou grupo relacionado) por vez

Rode testes apos cada upgrade

Commit: chore(deps): upgrade [pacote] to [versao]

Se testes falham, va para Fase 3 antes de continuar

Fase 3: Fix

Corrija API changes, type errors, deprecations

Atualize configuracao se necessario

Commit separado: fix(deps): adapt to [pacote] v[versao] changes

Fase 4: Verify

Rode suite completa de testes

Rode build e lint

Verifique deprecation warnings no output

Crie .spec/workflows/upgrades/SUMMARY.md:

Deps upgradados (from -> to)
Breaking changes e como foram resolvidos
Upgrades adiados e por que

Dependency Upgrade — Upgrade seguro

4 fases com artefatos em .spec/workflows/upgrades/.

Fase 1: Assess

Liste dependencias desatualizadas: npm outdated / equivalente
Para cada upgrade alvo:
- Leia changelog / release notes
- Identifique breaking changes
- Verifique migration guides
- Avalie impacto no codebase (grep por APIs afetadas)
Priorize: quais agora, quais adiar
Crie .spec/workflows/upgrades/ASSESSMENT.md:
- Lista com current -> target versions
- Breaking changes por dependencia
- Ordem de upgrade (deps antes de dependents)
- Risk assessment
Gate: Confirme scope com humano

Fase 2: Upgrade

Upgrade UMA dependencia (ou grupo relacionado) por vez
Rode testes apos cada upgrade
Commit: chore(deps): upgrade [pacote] to [versao]
Se testes falham, va para Fase 3 antes de continuar

Fase 3: Fix

Corrija API changes, type errors, deprecations
Atualize configuracao se necessario
Commit separado: fix(deps): adapt to [pacote] v[versao] changes

Fase 4: Verify

Rode suite completa de testes
Rode build e lint
Verifique deprecation warnings no output
Crie .spec/workflows/upgrades/SUMMARY.md:
- Deps upgradados (from -> to)
- Breaking changes e como foram resolvidos
- Upgrades adiados e por que