project-rename — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited project-rename (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Systematic checklist for renaming a project across every layer. Run each phase in order.
grep -rn "old_name\|old-name\|OldName\|OLD_NAME\|oldname" \
--include='*.{ts,tsx,js,py,md,json,yaml,yml,tf,sql,toml,cfg,conf,env,sh}' \
--exclude-dir=node_modules --exclude-dir=.git --exclude-dir=contracts/lib .See references/terraform-patterns.md for detailed Terraform rename patterns and code examples.
| Item | What to rename |
|---|---|
| Resource prefix | name_prefix in main.tf |
| State backend key | S3 key in backend config |
| ECR repos | Repository names |
| ECS cluster & services | Cluster name, service names |
| IAM policies | Resource ARNs referencing old name |
| Secrets Manager paths | Secret path prefix |
| ALB & target groups | Via prefix (automatic) |
| Route53 records | Verify zone lookups match the domain |
| CloudWatch log groups | Log group paths |
Gotcha — ACM + Route53 zone mismatch: If the Terraform zone lookup references zone A but the ACM cert needs validation in zone B, cert validation fails silently. Ensure the zone lookup matches var.domain.
Destroy & recreate workflow:
terraform destroy -auto-approveaws ecr delete-repository --force, then terraform state rm.tf files with new namesterraform applyterraform importCopy each secret from old path to new path:
for secret in supabase admin-key commission contracts api-keys x402; do
VALUE=$(aws secretsmanager get-secret-value --secret-id "old/$secret" --query SecretString --output text)
aws secretsmanager create-secret --name "new/$secret" --secret-string "$VALUE"
done| File | What to rename |
|---|---|
| Dockerfiles | Linux user/group names, header comments, example commands |
| docker-compose*.yml | Service names, network names, image tags |
| .dockerignore | Header comments |
| Makefile | Echo messages, network names, image tags |
| nginx configs | Header comments |
| Item | Files |
|---|---|
| ECR repo names | deploy*.yml |
| ECS cluster/service names | deploy*.yml |
| Container names in task defs | deploy.yml + task-def-.json |
| AWS region (verify!) | all workflow files |
| CODEOWNERS | team name references |
| What to find | What to do |
|---|---|
OLD_NAME_* env var fallbacks | Remove the fallback, keep only new name |
old_prefix_* API key prefixes | Replace with new prefix |
Backward-compat aliases (OldClient = NewClient) | Delete them |
| Rate limit prefix checks in middleware | Update to new prefix |
| Storage bucket references | Update bucket names |
| i18n keys referencing old name | Rename keys + update all locales |
| SDK/CLI env var fallbacks | Remove all old fallback chains |
Update: README.md, CLAUDE.md, SPEC.md, PLAN.md, agent-card.json, IDEA.yaml — project name, URLs, infrastructure details, deploy commands, secret paths, ECR repos.
grep -rn "old_name\|old-name\|OldName\|OLD_NAME" \
--include='*.{ts,tsx,js,py,md,json,yaml,yml,tf,toml,cfg,conf,sh}' \
--exclude-dir=node_modules --exclude-dir=.git --exclude-dir=contracts/lib .Do NOT rename: immutable on-chain contracts, historical SQL migrations, git history, third-party libraries.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.