From renovate-check
Run Renovate locally in dry-run mode to get a list of available dependency updates for the current working directory, then offer to apply them
How this skill is triggered — by the user, by Claude, or both
Slash command
/renovate-check:renovate-checkThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run Renovate in `--platform=local` mode to discover available dependency updates by analyzing the **local** files in the current working directory. No PRs or branches are created. The `--platform=local` mode automatically implies `dryRun=lookup`.
Run Renovate in --platform=local mode to discover available dependency updates by analyzing the local files in the current working directory. No PRs or branches are created. The --platform=local mode automatically implies dryRun=lookup.
Before running Renovate, check if the project has a Renovate config file. Search these standard locations (in order):
renovate.jsonrenovate.json5.renovaterc.renovaterc.json.github/renovate.json.github/renovate.json5Also check if package.json exists and contains a "renovate" key.
If a config file is found:
--require-config=optional so Renovate reads it but does not fail if it's missing--require-config=ignored — this would skip the config entirelyIf NO config file is found:
--require-config=ignored as fallbackUse npx to run Renovate in local platform mode. This analyzes the current directory without cloning anything from GitHub.
A GITHUB_COM_TOKEN is still needed for changelog lookups and to avoid rate limiting against package registries.
When config exists:
GITHUB_COM_TOKEN="$(gh auth token)" \
RENOVATE_LOG_FILE=/tmp/renovate-output.ndjson \
RENOVATE_LOG_FILE_LEVEL=debug \
LOG_LEVEL=info \
npx --yes --package renovate -- renovate \
--platform=local \
--onboarding=false \
--require-config=optional
When no config exists:
GITHUB_COM_TOKEN="$(gh auth token)" \
RENOVATE_LOG_FILE=/tmp/renovate-output.ndjson \
RENOVATE_LOG_FILE_LEVEL=debug \
LOG_LEVEL=info \
npx --yes --package renovate -- renovate \
--platform=local \
--onboarding=false \
--require-config=ignored
Run this command from the project's working directory (use cd if needed).
IMPORTANT: Always use full flag names (e.g. --yes, --package). Never use short flags.
After Renovate finishes, parse the NDJSON log file with jq to extract a clean list of available updates:
jq --raw-output '
select(.msg == "packageFiles with updates") |
.config | to_entries[] |
.key as $manager |
.value[] |
.packageFile as $file |
.deps[]? |
select(.updates | length > 0) |
"\($manager) | \($file) | \(.depName) | \(.currentValue // .currentDigest // "n/a") -> \(.updates[0].newVersion // .updates[0].newValue // .updates[0].newDigest // "n/a") (\(.updates[0].updateType))"
' /tmp/renovate-output.ndjson
Format the extracted updates as a clear, readable markdown table for the user:
| Manager | File | Dependency | Current | Available | Type |
|---|
Group by manager for readability. If no updates are found, report that all dependencies are up to date and skip to clean up (step 8).
If ANY of the found updates have updateType equal to major, research migration guides for each one before asking the user what to apply.
For each major update:
Use WebSearch to search for a migration guide. Use queries like:
"<depName>" migrate v<currentMajor> to v<newMajor>"<depName>" upgrade guide v<newMajor>"<depName>" breaking changes v<newMajor>"<depName>" v<newMajor> changelog"<chartName>" changelog v<newVersion>If a migration guide / changelog / upgrade guide is found, use WebFetch to read it and extract a concise summary of breaking changes.
Present the migration summary to the user alongside the updates table. Format:
### Major update: <depName> <currentVersion> -> <newVersion>
**Breaking changes:**
- <bullet point summary of key breaking changes>
- ...
**Migration guide:** <URL>
If no migration guide is found, note that explicitly: "No migration guide found for v -> v. Review the release notes manually before upgrading."
This step is critical — major version bumps can break builds and deployments. The user needs this information to make an informed decision.
If major updates were found, present the migration summaries first, then ask.
Use AskUserQuestion to ask the user which updates they want to apply. Offer these options:
For each update the user approved, apply changes using the appropriate method for the manager type:
go get [email protected]
After all go get commands, run:
go mod tidy
Edit the workflow YAML files directly — replace the old version tag with the new one in uses: lines. Use the Edit tool for this.
Edit the Containerfile/Dockerfile directly — replace the old image tag with the new one. Use the Edit tool.
Edit the values.yaml file directly — replace the old image tag/version with the new one. Use the Edit tool.
Edit the ArgoCD Application YAML files directly — replace the old targetRevision value with the new version. Use the Edit tool.
Use the native package manager CLI to update (e.g. npm install package@version, pip install package==version, cargo update --package name).
After applying updates:
golangci-lint run for Go projects)go test ./... for Go projects)Do NOT commit changes automatically — leave that to the user.
Remove the temporary log file after parsing:
rm -f /tmp/renovate-output.ndjson
--platform=local analyzes the LOCAL files in the current directory, not the remote repository--platform=local automatically sets dryRun=lookup — do NOT pass --dry-run separately--onboarding=false is REQUIRED — without it Renovate crashes trying to create an onboarding branch in local modeargocd manager has NO default fileMatch pattern and requires explicit configuration in the project's renovate.json (e.g. "argocd": {"fileMatch": ["argocd/.+\\.yaml$"]})GITHUB_COM_TOKEN is needed even locally for changelog lookups and registry rate limitsgh auth token provides the token from GitHub CLIrm does not support --force, use -f insteadCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub lexfrei/ccc --plugin renovate-check