cleanup

Detect and remove orphaned AWS resources created by cdkd integration tests.

97|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/go-to-k/cdkd --skill cleanup-go-to-k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/cleanup
Command: npx skills add https://github.com/go-to-k/cdkd --skill cleanup-go-to-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and delete leftover AWS resources created by cdkd integration tests to keep environments clean and cost-efficient.

Core Features & Use Cases

  • Safe detection: Scans known cdkd test prefixes across regions to identify orphaned resources.
  • Optional deletion: Presents a confirm-before-delete flow and can run in detect-only mode by default.
  • Comprehensive coverage: Checks IAM roles, Lambda functions, S3 buckets, DynamoDB tables, ECR repos, SQS/SNS resources, and networking components.

Quick Start

Run the cleanup operation to detect and optionally purge orphaned resources left by integration tests.

Frequently Asked Questions about cleanup

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

FAQPage Schema
How do I clean up leftover AWS resources from integration tests?▼

To clean up leftover AWS resources from integration tests, the Skill scans known cdkd test prefixes across regions to identify and optionally delete orphaned resources via a confirm-before-delete flow.

What AWS resources do cdkd integration tests leave behind?▼

cdkd integration tests leave behind IAM roles, Lambda functions, S3 buckets, DynamoDB tables, ECR repos, SQS/SNS resources, and networking components that require automated cleanup detection.

Can I detect orphaned AWS test resources without deleting them?▼

Yes, you can detect orphaned AWS test resources without deleting them by running the operation in detect-only mode, which acts as a safe, audit-friendly dry-run that requires user confirmation before any deletion occurs.

Do I need AWS CLI and IAM access to remove orphaned test resources?▼

Yes, you need AWS CLI and AWS IAM access to enumerate and delete orphaned test resources, applying strict naming-pattern filters across multiple regions and account contexts to avoid unintended deletions.

What's the safest way to automate removal of leftover AWS test resources?▼

The safest way to automate removal of leftover AWS test resources is using strict naming-pattern filters across regions with a default detect-only dry-run mode and an explicit user confirmation step before deletion.