ai-standardize-renovate

To detect Renovate config drift, this Skill compares files like renovate.json and renovate.json5 against a canonical template, surfacing custom packageRules and automergeStrategy deviations before guiding interactive resolution.

You can standardize multiple conflicting Renovate config files by running the validation flow, which checks for duplicate files like .renovaterc and renovate.json5, then guides safe resolution across default branches before applying changes.

Yes, you can prevent accidental overwrites of custom packageRules because the standardize flow uses interactive AskUserQuestion prompts to require explicit user confirmation before writing any changes to Renovate config files.

Renovate config drift occurs when files deviate from canonical templates via custom matchPackageNames or commitMessagePrefix overrides, which can break devops automation workflows and project processes if silently overwritten.

Yes, the Renovate standardization workflow supports both library and service repositories by scaffolding and enforcing canonical template selection with validation and cross-checks tailored for each repository type.

The best way to apply a canonical Renovate template safely is using an ask-before-write workflow that surfaces automergeStrategy deviations and requires explicit confirmation, ensuring custom settings are reviewed rather than lost.