renovate-image-guider

Trace Renovate image version bumps to upstream evidence and validate Pulumi deployments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill renovate-image-guider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: renovate-image-guider
Source: https://github.com/spigell/my-agents/tree/main/.agents/skills/renovate-image-guider
Command: npx skills add https://github.com/spigell/my-agents --skill renovate-image-guider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents risky container image updates by tracing Renovate changes back to upstream release evidence and then validating the deployment path before any apply.

Core Features & Use Cases

  • Renovate PR impact tracing: Reads a Renovate image PR, identifies bumped managed images, and maps each Spigell-owned image to the correct my-images lookup query term.
  • Evidence-backed upstream review: Traces the version bump chain across merged spigell/my-images PRs and reads their contents for upstream release/PR links, while enforcing strict “no guessing” evidence rules.
  • Special-case changelog for closed-source agy: Uses the Antigravity manifest service to download the agy binary and runs agy changelog as primary evidence.
  • Guardrailed deploy validation: Posts a consolidated pre-deploy risk review comment, then delegates Pulumi preview/apply via the shared pulumi-deployer skill with rollback protection and protected-change refusal.
  • Failure handling and automated update lock: If preview/apply fails or protected changes are detected, it blocks merge and writes a targeted renovate.json lock for the exact failing image package name.

Quick Start

Ask the agent to run the review-renovate-pr workflow for your my-agents Renovate PR and produce a consolidated AI Image Update Risk Review, followed by Pulumi deploy validation via pulumi-deployer.

Frequently Asked Questions about renovate-image-guider

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Renovate image PRs against upstream release evidence?

To validate Renovate image PRs, trace version bumps to upstream release evidence by reading PR metadata, resolving the spigell/my-images chain, and enforcing strict no-guessing rules before deployment, ensuring risky container updates are blocked.

How does Pulumi deployment validation work with Renovate container updates?

Pulumi deployment validation delegates preview and apply operations through a shared pulumi-deployer skill with rollback protection, refusing protected changes and automatically locking the failing image package in renovate.json if validation fails.

Can I trace closed-source image changelogs when reviewing Renovate PRs?

Yes, you can trace closed-source image changelogs for the agy package by using the Antigravity manifest service to download the agy binary and running agy changelog as the primary evidence source for your review.

What happens when a Renovate image update fails Pulumi preview or apply?

When Pulumi preview or apply fails, the workflow blocks the PR merge and writes a targeted renovate.json lock for the exact failing image package name, preventing Renovate from re-attempting the broken update.

Do I need github-mcp tools to review Renovate PRs for container images?

Yes, github-mcp tools are required to read PR contents and post comments during the Renovate image review process, enabling the workflow to fetch PR metadata and post the consolidated pre-deploy risk review comment.

How do I handle skipped versions when tracing Renovate image bumps?

Handling skipped versions requires strict evidence guards during chain resolution across merged spigell/my-images PRs, enforcing no-guessing rules to ensure every skipped version is traced to valid upstream release evidence.