Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

renovate-pr-review

Estrellas8

Forks0

Actualizado6 de julio de 2026 a las 13:09

Review a Renovate PR before merging — read the changelog, diff values against this repo's overrides, check e2e status, flag major bumps, and produce a merge checklist. Triggers on "review this renovate PR", "should I merge this chart bump", "is this renovate PR safe".

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

dark-vex

dark-vex/infra-cd

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	renovate-pr-review
description	Review a Renovate PR before merging — read the changelog, diff values against this repo's overrides, check e2e status, flag major bumps, and produce a merge checklist. Triggers on "review this renovate PR", "should I merge this chart bump", "is this renovate PR safe".

Renovate PR Review Skill

Use this skill when asked to review a Renovate-authored PR (Helm chart bump, Terraform provider/module bump, GitHub Action digest bump) before merging.

Review steps

Read the changelog. Renovate PR bodies link the upstream release notes/changelog for the version range being bumped — follow that link (or mcp__github__get_release_by_tag / search_commits on the upstream repo if the PR body doesn't include one) and read what actually changed, not just the version numbers.
Diff values against this repo's overrides. For a HelmRelease bump, check whether any values key this repo explicitly sets (.spec.values in the release.yml) was renamed, deprecated, or had its default/schema changed in the new chart version — a values key silently becoming a no-op is a real, historically-seen failure mode in this repo (see the secrets-management skill's example, and the A9 securityContext work, where wrong/renamed keys silently dropped intended config). For a Terraform provider bump, check the provider's changelog for breaking schema changes to resources/data sources this repo actually uses.
Check e2e status. For anything touching clusters/**, confirm validate-kubenuc.yml / validate-k8s-vms.yml ran and passed — a green Renovate PR without e2e having run at all is not evidence of safety.
Flag majors. A major version bump (chart vX.0.0, provider major) needs more scrutiny than a patch/minor — call this out explicitly in the review rather than treating all Renovate PRs the same.
Merge checklist. Summarize as a short checklist: changelog reviewed (yes/no + any breaking changes found), values/schema compatibility checked, e2e status, major-bump flag, recommendation (merge / merge with a follow-up values fix / hold for manual testing).

Scope notes

Don't manually edit chart versions Renovate owns (see root CLAUDE.md rule 6) — this skill is for reviewing Renovate's own PRs, not hand-bumping versions.
If review turns up a required values change (e.g. a renamed key), make that fix as a follow-up commit on the Renovate PR's branch (or a separate PR if Renovate doesn't allow pushes to its branch) rather than blocking the bump indefinitely — see the flux-operations and chart-specific patterns in terraform-operations/op-terraform for the values conventions to preserve.

Más de este repositorio

mismo repositorio

app-troubleshooting

dark-vex/infra-cd

Diagnose a broken/slow/crashlooping app in kubenuc or k8s-vms-daniele — gather evidence via Graylog/Grafana/kubectl before asking the user anything. Triggers on "X is down", "X is crashlooping", "X is erroring", "X is slow", "why did X restart".

2026-07-128

documentation

dark-vex/infra-cd

Route documentation/notes to the right destination (Confluence, README/CLAUDE.md, Obsidian, or NetBox) based on content type, and confirm the exact destination with the user before writing anything. Also invoke proactively — before opening a PR — when the change is a new operational gotcha, an incident, a security-hardening trade-off, a version-pin rationale, a new app/cluster, or a structural Terraform/infra change, to decide whether README.md, a CLAUDE.md, or Confluence needs updating.

2026-07-128

cluster-operations

dark-vex/infra-cd

Cluster lifecycle operations — setting up new clusters, kubenuc-test overlay pattern, kustomize patch conventions, and FluxCD bootstrap structure for infra-cd clusters.

2026-07-128

grafana-cardinality-guard

dark-vex/infra-cd

Before adding any new Prometheus scrape target or exporter, check the active-series budget in Grafana Cloud and propose write_relabel drops if needed. Triggers on "add a scrape config", "add an exporter", "enable metrics for X", "add a ServiceMonitor". Gates any change that could grow active series count.

2026-07-068

ansible-operations

dark-vex/infra-cd

Ansible playbook/role conventions, Molecule testing patterns, and ansible-agent invocation for the infra-cd repository.

2026-07-068

ci-workflows

dark-vex/infra-cd

GitHub Actions workflow patterns for infra-cd — Terraform CI (fmt/init/validate/plan/apply), cluster validation (k3s + FluxCD + Robot Framework), Flux cron updates, and runner selection.

2026-07-068

name	renovate-pr-review
description	Review a Renovate PR before merging — read the changelog, diff values against this repo's overrides, check e2e status, flag major bumps, and produce a merge checklist. Triggers on "review this renovate PR", "should I merge this chart bump", "is this renovate PR safe".

Renovate PR Review Skill

Use this skill when asked to review a Renovate-authored PR (Helm chart bump, Terraform provider/module bump, GitHub Action digest bump) before merging.

Review steps

Read the changelog. Renovate PR bodies link the upstream release notes/changelog for the version range being bumped — follow that link (or mcp__github__get_release_by_tag / search_commits on the upstream repo if the PR body doesn't include one) and read what actually changed, not just the version numbers.
Diff values against this repo's overrides. For a HelmRelease bump, check whether any values key this repo explicitly sets (.spec.values in the release.yml) was renamed, deprecated, or had its default/schema changed in the new chart version — a values key silently becoming a no-op is a real, historically-seen failure mode in this repo (see the secrets-management skill's example, and the A9 securityContext work, where wrong/renamed keys silently dropped intended config). For a Terraform provider bump, check the provider's changelog for breaking schema changes to resources/data sources this repo actually uses.
Check e2e status. For anything touching clusters/**, confirm validate-kubenuc.yml / validate-k8s-vms.yml ran and passed — a green Renovate PR without e2e having run at all is not evidence of safety.
Flag majors. A major version bump (chart vX.0.0, provider major) needs more scrutiny than a patch/minor — call this out explicitly in the review rather than treating all Renovate PRs the same.
Merge checklist. Summarize as a short checklist: changelog reviewed (yes/no + any breaking changes found), values/schema compatibility checked, e2e status, major-bump flag, recommendation (merge / merge with a follow-up values fix / hold for manual testing).

Scope notes

Don't manually edit chart versions Renovate owns (see root CLAUDE.md rule 6) — this skill is for reviewing Renovate's own PRs, not hand-bumping versions.
If review turns up a required values change (e.g. a renamed key), make that fix as a follow-up commit on the Renovate PR's branch (or a separate PR if Renovate doesn't allow pushes to its branch) rather than blocking the bump indefinitely — see the flux-operations and chart-specific patterns in terraform-operations/op-terraform for the values conventions to preserve.