project-rename

Rename projects across Terraform, Docker, CI/CD, DNS, and documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/UltravioletaDAO/execution-market --skill project-rename
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-rename
Source: https://github.com/UltravioletaDAO/execution-market/tree/main/.agents/skills/project-rename
Command: npx skills add https://github.com/UltravioletaDAO/execution-market --skill project-rename

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rename a project across every layer — code, infrastructure, Docker, CI/CD, DNS, docs, SDKs, and environment variables — to ensure consistent branding and references across the entire deployment.

Core Features & Use Cases

  • Multi-phase rename workflow covering IaC (Terraform), secret paths, Docker images, CI/CD pipelines, DNS records, docs, and SDK references.
  • Variant-wide search & replace guidance: generate and apply a comprehensive rename map across Terraform, Kubernetes manifests, scripts, and docs.
  • Real-world use case: when rebranding a product, ensuring all references—from ECR repos to Route53 records, Docker tags, and environment variables—are updated consistently, avoiding drift and outages.

Quick Start

Identify the old and new project names, then run the phased rename workflow to apply changes across Terraform, secret paths, container images, and docs.

Frequently Asked Questions about project-rename

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

FAQPage Schema
How do I rename a project across Terraform, Docker, and CI/CD pipelines?

To rename a project across Terraform, Docker, and CI/CD, apply a multi-phase rename workflow that generates a comprehensive rename map for consistent propagation across infrastructure, secret paths, and documentation.

What is the best way to rebrand a product across infrastructure and docs without causing outages?

The best way to rebrand a product without outages is coordinating end-to-end changes with validation and rollback safeguards across code, IaC, and docs to prevent drift in ECR repos and Route53 records.

Does a project rename workflow update DNS records and environment variables?

Yes, a project rename workflow updates DNS records and environment variables by applying variant-wide search and replace guidance across Kubernetes manifests, scripts, and configuration files.

Can I rollback infrastructure changes if a project rename causes deployment drift?

Yes, you can rollback infrastructure changes if a project rename causes deployment drift because the workflow coordinates end-to-end changes with validation and rollback safeguards across code, IaC, and docs.

What steps are needed to update Docker image tags and SDK references during a project rename?

To update Docker image tags and SDK references, identify old and new project names, run the phased rename workflow to apply changes across container images, and generate a comprehensive rename map for reliable propagation.