renovate
Assists with automating dependency updates across JavaScript, Python, Docker, Go, Rust, Terraform, and 50+ ecosystems using Renovate. Use when configuring update strategies, automerge policies, grouping rules, or scheduling to keep dependencies current. Trigger words: renovate, dependency updates, automerge, package rules, dependency management.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o renovate.zip https://jpskill.com/download/15338.zip && unzip -o renovate.zip && rm renovate.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/15338.zip -OutFile "$d\renovate.zip"; Expand-Archive "$d\renovate.zip" -DestinationPath $d -Force; ri "$d\renovate.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
renovate.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
renovateフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
Renovate
Overview
Renovate is an automated dependency update tool that scans repositories for dependency files across 50+ ecosystems (npm, pip, Docker, Go, Rust, Terraform, GitHub Actions) and creates pull requests with changelogs, release notes, and configurable automerge policies. It supports grouping, scheduling, and per-package rules to keep dependencies current without overwhelming teams.
Instructions
- When setting up Renovate, start with
config:recommendedwhich provides sensible defaults for grouping, scheduling, and automerge, then addrenovate.jsonto the repo root. - When configuring automerge, enable it for low-risk updates (
@types/*, devDependencies patches) and disable it for major updates, usingplatformAutomergefor GitHub's native merge feature. - When reducing PR noise, use
group:allNonMajorfor a single weekly PR covering all minor and patch updates, and group monorepo packages (React, Angular, Babel) together. - When setting schedules, configure update windows for low-traffic times (e.g.,
["after 9am and before 5pm every weekday"]) to avoid disrupting developers. - When defining package rules, use
matchPackageNames,matchPackagePatterns, andmatchUpdateTypesto set per-package automerge, grouping, and version strategies. - When handling version strategies, pin exact versions in applications for reproducibility and use ranges in libraries for compatibility.
Examples
Example 1: Configure Renovate for a production monorepo
User request: "Set up Renovate with automerge for safe updates and weekly batching"
Actions:
- Create
renovate.jsonextendingconfig:recommendedandschedule:weekly - Add package rules to automerge
@types/*and devDependency patches - Group React, Next.js, and testing library packages into single PRs
- Enable the dashboard issue for an overview of all pending updates
Output: A Renovate configuration that automerges safe updates, batches non-major changes weekly, and groups related packages.
Example 2: Manage Docker and Terraform dependency updates
User request: "Keep Docker base images and Terraform provider versions up to date"
Actions:
- Configure Renovate to scan Dockerfiles and
.tffiles - Set
matchDatasources: ["docker"]withautomerge: falsefor base image updates - Group Terraform providers by cloud provider (AWS, GCP, Azure)
- Enable vulnerability alerts to prioritize updates that fix known CVEs
Output: Automated PRs for Docker and Terraform dependency updates with grouped providers and security prioritization.
Guidelines
- Start with
config:recommendedsince it handles grouping, scheduling, and automerge sensibly. - Automerge
@types/*and devDependencies patches since they are low-risk and high-volume. - Group monorepo packages (React, Vue, Angular, Babel, Jest) into single PRs to reduce noise.
- Schedule updates for low-traffic times to avoid disrupting developers during peak hours.
- Pin exact versions in applications and use ranges in libraries.
- Review major updates manually since breaking changes require human judgment.