Dependency Upgrade Review with Claude Code: SKILL.md Template
A production playbook for dependency upgrade review in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Engineering teams managing package risk
The problem
Engineering teams managing package risk need dependency upgrade review to run repeatedly against lockfiles, changelogs, advisories, and test logs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach lockfiles, changelogs, advisories, and test logs per run, and let Argo turn the folder into a repeatable Claude Code execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For dependency upgrade review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run dependency upgrade review using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "dependency_upgrade_review".
Run this on Argo