br4zz4:no-digital-ocean

Name: br4zz4:no-digital-ocean
Availability: InStock
Author: oporpino

Detects and replaces Digital Ocean references with AWS equivalents in infra and config files.

Updated May 25, 2025

Search Tags:#code review #aws #migration #cleanup #infrastructure #ecr #digital ocean

Ready to run

npx skills add https://github.com/oporpino/commons --skill br4zz4-no-digital-ocean-oporpino

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: br4zz4:no-digital-ocean
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Ano-digital-ocean
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-no-digital-ocean-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After migrating from Digital Ocean to AWS, leftover references to Digital Ocean in infrastructure, CI, and configuration files cause broken deployments and confusion. This Skill ensures every file is scanned for stale Digital Ocean references and guides their replacement with the correct AWS equivalent. ## Core Features & Use Cases - Reference Detection: Scans files for known Digital Ocean patterns such as `registry.digitalocean.com`, `DO_TOKEN`, `doctl`, `digitalocean_database_cluster`, and `digitalocean_spaces`. - AWS Replacement Mapping: Provides a direct mapping table from Digital Ocean resources to AWS equivalents like ECR, IAM-based auth, `aws_rds_cluster`, and `aws_s3_bucket`. - Use Case: While reviewing a CI pipeline file, the Skill flags `CONTAINER_REGISTRY=registry.digitalocean.com/br4zz4` and instructs replacing it with the correct AWS ECR endpoint before proceeding. ## Quick Start Ask the AI to scan this repository for any remaining Digital Ocean references and replace them with the AWS equivalents.

Frequently Asked Questions about br4zz4:no-digital-ocean

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

FAQPage Schema

How do I find leftover Digital Ocean references in my codebase?▼

Search files for patterns like digitalocean, registry.digitalocean.com, DO_TOKEN, DIGITALOCEAN_, docr_token, doctl, digitalocean_database_cluster, and digitalocean_spaces. Any match is treated as a bug to fix immediately.

How to replace Digital Ocean container registry with AWS ECR?▼

Replace registry.digitalocean.com/br4zz4 with the correct AWS ECR endpoint URL, and swap docr_token authentication for ECR auth via IAM role or AWS_ACCESS_KEY_ID. Ask the user for the ECR URL if it is unknown.

What is the AWS equivalent of digitalocean_database_cluster?▼

The AWS replacement for digitalocean_database_cluster is aws_rds_cluster. Similarly, digitalocean_spaces maps to aws_s3_bucket for object storage.

Should I keep DO_TOKEN or digitalocean_access_token after migrating to AWS?▼

No. Both DO_TOKEN and digitalocean_access_token should be removed entirely since they are no longer needed after the migration to AWS. AWS authentication uses IAM roles or access keys instead.

When does this Digital Ocean cleanup rule apply?▼

It applies passively whenever any file being read contains a Digital Ocean reference, which must be fixed before continuing the main task. It also applies explicitly when auditing, migrating, or cleaning up DO references.