Menú
Use for dependency upgrades, vulnerability fixes, version conflicts, lockfiles, package managers, and migration risk.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use only when the user explicitly invokes this skill to map unresolved product, domain, repository, or delivery unknowns before choosing a path.
Use only when the user explicitly invokes this skill to create or resume a persistent file-based goal tracker across sessions.
Use only when the user explicitly invokes this skill to stress-test an existing plan or design through one load-bearing question at a time.
Use only when the user explicitly invokes this skill to evaluate a skill with representative cases, isolated runs, independent judging, and evidence-driven edits.
Use for a concrete defect or regression that needs reproduction, root-cause diagnosis, a fix, and regression validation. Do not trigger for routine localized edits or primarily performance-focused work.
Use when the requested feature genuinely spans at least two delivery layers such as frontend, backend, API, data, scripts, or tests. Do not expand a single-layer change into a full-stack workflow.
| name | dev-dependency-upgrade |
| description | Use for dependency upgrades, vulnerability fixes, version conflicts, lockfiles, package managers, and migration risk. |
| metadata | {"version":"0.3","updated":"2026-06-12"} |
Use this workflow when dependencies, lockfiles, package versions, or vulnerability fixes are in scope.
Identify ecosystems.
Read the source of truth.
Classify the change.
Plan safely.
Validate.
Return:
