triage-leaked-infra

Assess whether leaked AWS VPC infrastructure from HyperShift CI is safe to delete.

538|560|Updated Jan 18, 2021
One-click install
npx skills add https://github.com/openshift/hypershift --skill triage-leaked-infra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-leaked-infra
Source: https://github.com/openshift/hypershift/tree/main/.claude/skills/triage-leaked-infra
Command: npx skills add https://github.com/openshift/hypershift --skill triage-leaked-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HyperShift CI jobs leave behind orphaned AWS infrastructure (VPCs, NAT gateways, IAM roles, Route53 zones) that accumulates cost, but deleting the wrong resource can destroy a developer's active cluster. This Skill runs a rigorous, evidence-based triage so you know with confidence whether an infra set is safe to remove.

Core Features & Use Cases

  • Twelve-Check Safety Audit: Verifies protection tags, protected VPC names, protected developer usernames, expiration dates, CI naming patterns, OIDC S3 liveness, running EC2 instances, ROSA-managed resources, sub-resource inventory, Route53 zones, OIDC IAM providers, and orphaned IAM roles.
  • Empirical Verification Only: Every claim is backed by a live AWS CLI query against us-east-1 — no assumptions, no guessing.
  • Clear Verdicts: Produces a structured report table ending in SAFE TO DELETE, DO NOT DELETE, UNCERTAIN, or REQUIRES HUMAN DECISION based on non-negotiable verdict rules.
  • Use Case: You paste cleanleaked tool output showing a LEAKED verdict for infraID 00ab3695c5f73d4354b9. The Skill queries AWS, confirms the hex CI pattern, expired resources, no running instances, and no OIDC document, then reports SAFE TO DELETE.

Quick Start

Paste the cleanleaked output or a VPC ID and ask whether this leaked HyperShift CI infrastructure is safe to delete.

Frequently Asked Questions about triage-leaked-infra

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

FAQPage Schema
How do I check if a leaked AWS VPC is safe to delete?

Provide the VPC ID or infraID and the Skill runs twelve AWS CLI checks including protection tags, running EC2 instances, OIDC S3 liveness, and expiration dates. It returns a verdict of SAFE TO DELETE, DO NOT DELETE, or UNCERTAIN based on the results.

How to triage cleanleaked output from HyperShift CI?

Paste the cleanleaked infra set block directly into the conversation. The Skill extracts the infraID and VPC ID, then empirically verifies each safety condition with AWS queries in us-east-1 before issuing a verdict.

What makes a HyperShift infra set unsafe to delete?

A FAIL on any check blocks deletion: a do-not-delete or ci-cluster tag, a protected VPC name like hypershift-ci-2-vpc, a developer username in the infraID, an unexpired expirationDate, live OIDC documents in S3, running EC2 instances, or red-hat-managed ROSA resources.

Does the triage work if the VPC has no expirationDate tag?

Yes. When expirationDate is absent, the Skill derives resource age from the earliest creation timestamp of VPC endpoints or network interfaces. Resources older than 24 hours with a matching CI pattern pass; younger ones fail.

Which AWS region and permissions does the triage require?

All queries run against us-east-1 using the AWS CLI. You need read permissions for EC2, ELBv2, S3, Route53, and IAM in the HyperShift CI account to execute the describe, list, and head-object calls.