agntcms-rename-slug

Renaming page slugs atomically updates all related pages, drafts, and history in one operation. This skill validates both source and target slugs, checks for conflicts, and warns about broken external links before executing the rename.

Atomic slug renaming updates pages, drafts, and history simultaneously to prevent partial updates or data corruption. This ensures changing a page URL identifier in a content framework leaves no orphaned drafts or mismatched historical records.

When changing page URLs, this skill validates source and target slugs against specific rules and checks for conflicts with existing pages or drafts. It then calls a required endpoint to execute the fully validated renaming process.

Yes, you need a configured endpoint to handle the renaming process. This endpoint-driven skill calls your designated API to execute atomic slug updates only after completing all validation and conflict checks.

Yes, this skill generates a preview URL before finalizing the slug rename. This lets you review the target slug and identify broken external links before the atomic update is executed across the content framework.