home / skills / ehtbanton / claudeskillsrepo / renovate-config-generator

renovate-config-generator skill

safe

This skill generates a complete Renovate configuration automatically, enforcing best practices for automated dependency updates.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill renovate-config-generator

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

776 B

---
name: renovate-config-generator
description: Generate Renovate configuration for automated dependency updates. Triggers on "create renovate config", "generate renovate configuration", "renovate setup", "dependency updates config".
---

# Renovate Config Generator

Generate Renovate configuration for automated dependency update management.

## Output Requirements

**File Output:** `renovate.json` or `.renovaterc.json`
**Format:** Valid Renovate configuration
**Standards:** Renovate best practices

## When Invoked

Immediately generate a complete Renovate configuration with appropriate update rules.

## Example Invocations

**Prompt:** "Create renovate config with automerge for minor updates"
**Output:** Complete `renovate.json` with automerge and grouping rules.

Overview

This skill generates a complete Renovate configuration file to automate dependency updates across projects. It outputs a ready-to-use renovate.json or .renovaterc.json formatted to Renovate best practices. The configuration includes sensible defaults for update schedules, grouping, and automerge rules tailored to the prompt.

How this skill works

When triggered, the skill inspects the request for desired policies (automerge, schedule, grouping, package-ecosystems) and produces a valid Renovate configuration. It selects rules for lockfile maintenance, major/minor/patch behavior, dependency type filters, and branch naming. The output is a single JSON config that can be dropped into the repository root to enable Renovate.

When to use it

You want a ready-to-drop renovate.json to enable automated dependency updates.
You need automerge policies for safe minor/patch updates and manual review for majors.
You want grouped PRs by package type or update scope (e.g., all devDependencies).
You need a baseline Renovate config for a TypeScript project or monorepo.
You are setting update schedules to avoid CI or release window conflicts.

Best practices

Enable lockfile maintenance and separate lockfile updates to reduce PR noise.
Automerge only for patch/minor updates with passing CI and no breaking-change labels.
Group related updates (devDependencies, security fixes, lockfiles) to reduce churn.
Schedule major updates outside critical release windows and require review.
Use sensible branch name and PR title templates for traceability in CI.

Example use cases

Create renovate config with automerge for minor updates and CI check requirements.
Generate config for a TypeScript monorepo that groups workspace dependencies.
Produce a security-focused policy that prioritizes dependency-security updates.
Set up a weekday schedule to run Renovate without interfering with weekend releases.
Configure separate rules for Dockerfile, GitHub Actions, and npm updates.

FAQ

What file will the skill output?

A valid renovate.json or .renovaterc.json configuration file ready for repository root.

Can it enable automerge safely?

Yes — the default recommends automerge only for non-breaking minor/patch updates after passing CI.