RE

renaming-services

Updates service documentation filenames, slugs, and internal references across the repository.

Install

mkdir -p .claude/skills/renaming-services && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3989" && unzip -o skill.zip -d .claude/skills/renaming-services && rm skill.zip

Installs to .claude/skills/renaming-services

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Renames a service documentation file and updates all references. Use when renaming services, changing service slugs, fixing camelCase to kebab-case, or when service names change in the Coolify repository templates/compose/. Updates docs/services/, regenerates listings, and adds nginx redirects.
295 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Renames documentation files in docs/services/
  • →Updates service references in List.vue
  • →Regenerates internal service data files
  • →Updates nginx/redirects.conf paths
  • →Updates local logo asset files

How it works

Executes a git rename for the markdown file and triggers the automated pipeline to regenerate all dependent listing files and configuration maps.

Inputs & outputs

You give it
Old service name and new service name
You get back
Renamed markdown file and updated system references

When to use renaming-services

  • →Rename service documentation files
  • →Convert service slugs to kebab-case
  • →Update nginx redirects after changing service names

About this skill

Rename Service Documentation

The slug is the .mdx filename in content/docs/services/. The searchable catalog and categorized directory derive their entries from that page; neither generated output is hand-edited.

Workflow

1. Rename the Page

git mv content/docs/services/old-name.mdx content/docs/services/new-name.mdx

Use a lowercase kebab-case slug that matches the intended service identity. Confirm the relevant upstream template when choosing a new name; a display-title correction alone does not require changing the URL.

2. Check Title and Images

Update title and the body when the displayed name changes. If the icon was resolved from the old slug, either rename the local asset or keep the asset and set an explicit icon path:

icon: "/docs/images/services/old-name-logo.svg"

If renaming the asset, update frontmatter and body references too:

git mv public/images/services/old-name-logo.svg public/images/services/new-name-logo.svg

The resolver accepts an existing icon under /docs/images/services/. See IMAGES.md for naming and resolution details.

3. Preserve Old URLs

Add rules to nginx/redirects.conf that handle both prefixed and stripped requests, with optional trailing slashes:

location ~ ^(?:/docs)?/services/old-name/?$ { return 301 "/docs/services/new-name"; }

If an older knowledge-base route existed, preserve that too:

location ~ ^(?:/docs)?/knowledge-base/services/old-name/?$ { return 301 "/docs/services/new-name"; }

Check existing rules for shadowing and loops. Keep older redirects working, preferably pointing straight to the final destination. See CLAUDE.md for the deployment's /docs prefix handling.

4. Update Authored References

rg -n 'old-name' content/docs src public templates

Update relevant handwritten links and image references, plus any explicit section meta.json entry. Individual service pages normally use the generated catalog rather than individual sidebar entries. Leave intentional upstream names and historical references intact.

5. Regenerate and Verify

bun run generate:services
bun run check:redirects -- --base origin/next

Check src/generated/services.json and content/docs/services/all.mdx for the new slug and destination. Do not edit either output by hand. When committing, include the rename, any asset changes, cross-links, redirect rules, and both generated outputs.

Verification

  • content/docs/services/new-name.mdx exists; the old source file is gone.
  • The title, category, icon, and disabled state remain correct after regeneration.
  • The old slug is absent from catalog records and directory links.
  • The new page and catalog card work at http://localhost:3000/docs/services/new-name and /docs/services/overview.
  • The redirect checker passes for prefixed, stripped, and trailing-slash old URLs. Nginx redirects are not executed by the Vite development server; verify HTTP redirect behavior in a deployment or Nginx preview when available.

See TESTING.md for generator checks.

Related Skills

When not to use it

  • →When the service name is being changed in upstream JSON but not in the documentation repository
  • →When you need to manually edit service listing files

Prerequisites

gitbash

Limitations

  • →Does not automatically handle external search engine index updates
  • →Requires manual intervention if logo naming conventions vary significantly from standard
  • →Only supports lowercase kebab-case naming

How it compares

It automates the multi-file synchronization required for a service rename instead of relying on manual file edits.

Compared to similar skills

renaming-services side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
renaming-services (this skill)16moReviewBeginner
deepwiki-rs251yReviewIntermediate
python-code-style99moReviewIntermediate
code-review-excellence198moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

deepwiki-rs

sopaco

AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.

25170

python-code-style

wshobson

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

971

code-review-excellence

wshobson

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

1958

code-walk-thru

pchalasani

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

670

cookbook-audit

anthropics

Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.

568

schema-markup

davila7

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

1042

Search skills

Search the agent skills registry