Upgrade Solidity Contracts
Upgrade Solidity smart contracts using OpenZeppelin proxy patterns. Use when users need to: (1) make contracts upgradeable with UUPS, Transparent, or Beacon proxies, (2) write initializers instead of constructors, (3) use the Hardhat or Foundry upgrades plugins, (4) understand storage layout rules and ERC-7201 namespaced storage, (5) validate upgrade safety, (6) manage proxy deployments and upgrades, or (7) understand upgrade restrictions between OpenZeppelin Contracts major versions.
Install
/plugin marketplace add OpenZeppelin/openzeppelin-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add OpenZeppelin/openzeppelin-skills --skill upgrade-solidity-contractsgit clone --depth 1 https://github.com/OpenZeppelin/openzeppelin-skills.git /tmp/openzeppelin-skills
mkdir -p ~/.claude/skills
cp -r /tmp/openzeppelin-skills/skills/upgrade-solidity-contracts ~/.claude/skills/upgrade-solidity-contractsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Solidity Upgrades ## Contents - [Proxy Patterns Overview](#proxy-patterns-overview) - [Upgrade Restrictions Between Major Versions (v4 → v5)](#upgrade-restrictions-between-major-versions-v4--v5) - [Writing Upgradeable Contracts](#writing-upgradeable-contracts) - [Hardhat Upgrades Workflow](#hardhat-upgrades-workflow) - [Foundry Upgrades Workflow](#foundry-upgrades-workflow) - [Handling Upgrade Validation Issues](#handling-upgrade-validation-issues) - [Upgrade Safety Checklist](#upgrade-safety-checklist) ## Proxy Patterns Overview | Pattern | Upgrade logic lives in | Best for | |---------|----------------------|----------| | **UUPS** (`UUPSUpgradeable`) | Implementation contract (override `_authorizeUpgrade`) | Most projects — lighter proxy, lower deploy gas | | **Transparent** | Separate `ProxyAdmin` contract | When admin/user call separation is critical — admin cannot accidentally call implementation functions | | **Beacon** | Shared beacon contract | Multiple proxies sharing one implementation — upgrading the beacon atomically upgrades all proxies | All three use EIP-1967 storage slots for the implementation address, admin, and beacon.
Details
- Skill name
upgrade-solidity-contracts- Repository
- OpenZeppelin/openzeppelin-skills
- Path
skills/upgrade-solidity-contracts/SKILL.md- License
- AGPL-3.0
- Repo updated
- 11 November 2026
FAQ
What does the Upgrade Solidity Contracts skill do?
Upgrade Solidity smart contracts using OpenZeppelin proxy patterns. Use when users need to: (1) make contracts upgradeable with UUPS, Transparent, or Beacon proxies, (2) write initializers instead of constructors, (3) use the Hardhat or Foundry upgrades plugins, (4) understand storage layout rules and ERC-7201 namespaced storage, (5) validate upgrade safety, (6) manage proxy deployments and upgrades, or (7) understand upgrade restrictions between OpenZeppelin Contracts major versions.
How do I install the Upgrade Solidity Contracts skill?
Claude Code plugin: /plugin marketplace add OpenZeppelin/openzeppelin-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Upgrade Solidity Contracts popular?
It lives in OpenZeppelin/openzeppelin-skills, which has 223 GitHub stars and 38 forks.
Related skills
Develop Secure Contracts
223OpenZeppelin/openzeppelin-skills
Develop secure smart contracts using OpenZeppelin Contracts libraries. Use when users need to integrate OpenZeppelin library components — including token standards (ERC20, ERC721, ERC1155), access control (Ownable, AccessControl, AccessManager), security primitives (Pausable, ReentrancyGuard), governance (Governor, timelocks), or accounts (multisig, account abstraction) — into existing or new contracts. Covers pattern discovery from library source, CLI contract generators, and library-first integration. Supports Solidity, Cairo, Stylus, Stellar, and Sui Move.
Migrate Defender to Cre
223OpenZeppelin/openzeppelin-skills
Migrate OpenZeppelin Defender Actions, Autotasks, Monitors and scheduled or Relayer-backed workflows to Chainlink CRE. Use when assessing CRE migration feasibility, adapting an existing Defender workflow, or validating its event delivery and onchain permissions. Does not cover migration to the self-hosted OpenZeppelin Relayer when CRE is not requested.
Review Sui Contracts
223OpenZeppelin/openzeppelin-skills
Review Sui Move code that integrates OpenZeppelin Contracts for Sui against the library's own patterns and conventions. Use this when a developer wants their integration checked before shipping. Triggers: "review my Sui Move code", "am I using OpenZeppelin correctly", "check this integration", "is this idiomatic", "review before audit". Checks correct use of OZ primitives, deviations from examples/doc-comments, upheld invariants, test coverage, and code-quality/style. This is an AI code review, not a formal security audit.
Upgrade Stellar Contracts
223OpenZeppelin/openzeppelin-skills
Upgrade Stellar/Soroban smart contracts using OpenZeppelin's upgradeable module. Use when users need to: (1) make Soroban contracts upgradeable via native WASM replacement, (2) use Upgradeable or UpgradeableMigratable derive macros, (3) implement atomic upgrade-and-migrate patterns with an Upgrader contract, (4) ensure storage key compatibility across upgrades, or (5) test upgrade paths for Soroban contracts.
Upgrade Cairo Contracts
223OpenZeppelin/openzeppelin-skills
Upgrade Cairo smart contracts using OpenZeppelin's UpgradeableComponent on Starknet. Use when users need to: (1) make Cairo contracts upgradeable via replace_class_syscall, (2) integrate the OpenZeppelin UpgradeableComponent, (3) understand Starknet's class-based upgrade model vs EVM proxy patterns, (4) ensure storage compatibility across upgrades, (5) guard upgrade functions with access control, or (6) test upgrade paths for Cairo contracts.
Upgrade Stylus Contracts
223OpenZeppelin/openzeppelin-skills
Upgrade Stylus smart contracts using OpenZeppelin proxy patterns on Arbitrum. Use when users need to: (1) make Stylus Rust contracts upgradeable with UUPS or Beacon proxies, (2) understand Stylus-specific proxy mechanics (logic_flag, WASM reactivation), (3) integrate UUPSUpgradeable with access control, (4) ensure storage compatibility across upgrades, or (5) test upgrade paths for Stylus contracts.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.