Pulumi Upgrade Provider

Automates the gnarly process of upgrading Pulumi provider repositories to new upstream versions by running the upgrade-provider tool in a loop and fixing its common failure modes. You'll mainly use this when a provider needs to track a new version of its upstream Terraform provider or SDK. It handles the tedious stuff like patch conflicts, missing module mappings, and go.mod replacement directives, then creates a PR when it succeeds. The skill enforces strict guardrails around git operations since upgrade-provider manages branches and commits itself. Includes a reference doc for known error patterns and knows when to bail out and ask for human judgment on breaking changes or architectural decisions.

skills.sh installs: 702
GitHub stars: 79
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pulumi/agent-skills --skill pulumi-upgrade-provider --agent claude-code

Installs into .claude/skills of the current project.

Files

Pulumi Upgrade Provider

Overview

Run upgrade-provider --no-submit, fix known failures, and rerun until success. During the run loop, the tool owns branch and generated-commit state but does not push or mutate GitHub. After success, review and correct the local result before submitting it using the plan printed by the tool.

Preflight

Record existing changes as the pre-upgrade baseline:

baseline_file="${TMPDIR:-/tmp}/upgrade-provider-$(basename "$PWD")-baseline.txt"
git status --short --untracked-files=all | tee "$baseline_file"

Existing changes do not block the upgrade, but the tool stages broadly and may include them in generated commits. If practical, isolate clearly unrelated work in another branch or worktree, move local-only files, or add untracked local artifacts to .git/info/exclude. Otherwise proceed and carry this baseline into the final review. Do not add a repository .gitignore rule unless the path should be ignored for all contributors.