anton-upgrade-audit

Classify Renovate PRs and cluster-deprecation signals into a prioritized upgrade plan.

3|Updated May 13, 2025

Search Tags:#audit #kubernetes #upgrade #nova #renovate #dependency-dashboard #kubent

Ready to run

npx skills add https://github.com/wcygan/anton --skill anton-upgrade-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: anton-upgrade-audit
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/anton-upgrade-audit
Command: npx skills add https://github.com/wcygan/anton --skill anton-upgrade-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a read-only triage workflow for upgrades across Renovate PRs, the Dependency Dashboard, and live-cluster deprecation audits, enabling safe, planned changes without mutating the repo or the cluster.

Core Features & Use Cases

Classifies open Renovate PRs by type/area to surface a tiered merge order and guide release planning.
Reads the Renovate Dependency Dashboard (issue #10) to surface items not yet PR'd and track drift.
Performs live-cluster deprecation audits with kubent, pluto, nova to identify API removals, manifest drift, and chart/version mismatches.
Enforces read-only behavior and hands off upgrade work to appropriate workflows (e.g., upgrade-talos-or-k8s).

Quick Start

Run the anton-upgrade-audit skill to enumerate open Renovate PRs, dependency-dashboard items, and cluster-deprecation findings.

Frequently Asked Questions about anton-upgrade-audit

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

FAQPage Schema

How do I triage open Renovate PRs to plan safe upgrades?▼

To triage open Renovate PRs for safe upgrades, classify them by type and area to produce a tiered merge order. This read-only process outputs a structured, prioritized plan with audit findings without mutating your repository or cluster.

What is a read-only Kubernetes cluster deprecation audit?▼

A read-only Kubernetes cluster deprecation audit uses tools like kubent, pluto, and nova to identify API removals, manifest drift, and chart or version mismatches. It generates prioritized tiering findings without modifying the live cluster.

How do I track dependency drift using the Renovate Dependency Dashboard?▼

Tracking dependency drift with the Renovate Dependency Dashboard involves reading issue #10 to surface items not yet PR'd. This read-only audit classifies dashboard items to guide upgrade handoffs and tiered merge ordering.

Can I use kubent and nova to detect Kubernetes API removals safely?▼

Yes, you can use kubent and nova to safely detect Kubernetes API removals by enforcing read-only behavior during the audit. The process identifies deprecated APIs and outputs a structured upgrade plan without applying changes.

Does the Renovate upgrade audit workflow mutate my live cluster?▼

No, the Renovate upgrade audit workflow does not mutate your live cluster. It enforces strict read-only behavior to classify PRs and deprecation signals, handing off the actual upgrade work to appropriate separate workflows.

What is the best way to prioritize Kubernetes dependency upgrades?▼

The best way to prioritize Kubernetes dependency upgrades is to cluster deprecation signals and classify open PRs into a tiered merge order. This method identifies API removals and drift to produce a structured, prioritized plan.