fix-up-redirectors

Automate removal of stale Unreal Engine ObjectRedirector assets in Perforce environments.

3|1|Updated Feb 21, 2026

Search Tags:#automation #cleanup #asset management #perforce #unreal engine #redirectors

Ready to run

npx skills add https://github.com/kitaekatt/plugins-kit --skill fix-up-redirectors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-up-redirectors
Source: https://github.com/kitaekatt/plugins-kit/tree/main/plugins/unreal-kit/skills/fix-up-redirectors
Command: npx skills add https://github.com/kitaekatt/plugins-kit --skill fix-up-redirectors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves the common Unreal Engine issue where redirector assets accumulate and cause editor stalls or broken references, particularly in Perforce-backed projects where manual cleanup is risky and time-consuming.

Core Features & Use Cases

Intelligent Classification: Automatically categorizes redirectors into safe-to-fix, orphaned, or broken sets based on P4 status and referencer existence.
Safety-First Pipeline: Implements a multi-phase workflow including code-reference filtering and directory-sampled test slices to prevent runtime regressions.
Use Case: Use this after a large-scale asset rename or move operation to purge dead pointers and fix up remaining redirectors without breaking C++ or Blueprint references.

Quick Start

Run the fix-up-redirectors skill to scan your project and follow the interactive menu to select a safe cleanup operation.

Frequently Asked Questions about fix-up-redirectors

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

FAQPage Schema

How do I clean up Unreal Engine redirectors in Perforce safely?▼

Cleaning up Unreal Engine redirectors in Perforce safely requires heuristic-based reference scanning across source code and asset registries to prevent broken references, which this skill automates using atomic changelist operations.

Why do stale redirectors cause editor stalls in Unreal Engine?▼

Stale redirectors cause Unreal Engine editor stalls because they accumulate as dead pointers after asset moves or renames, creating broken references that the editor must resolve manually during load operations.

Can I remove redirectors without breaking C++ or Blueprint references?▼

You can remove redirectors without breaking C++ or Blueprint references by implementing code-reference filtering and directory-sampled test slices, which categorize redirectors into safe-to-fix, orphaned, or broken sets before deletion.

Do I need Perforce CLI and Unreal Engine Python API to automate redirector fix-up?▼

Yes, automating redirector fix-up requires Perforce CLI integration and Unreal Engine Python API access to execute atomic changelist operations and perform heuristic-based scanning across your project's asset registries and source code.

What is the best way to purge dead pointers after an asset rename in Unreal Engine?▼

The best way to purge dead pointers after an asset rename in Unreal Engine is to use an automated pipeline that categorizes redirectors by Perforce status and referencer existence, ensuring you only delete safe-to-fix pointers.

When should I not use automated redirector cleanup in my project?▼

You should avoid automated redirector cleanup when your project lacks Perforce CLI integration or Unreal Engine Python API access, as the skill requires these dependencies to perform atomic changelist operations and validate references safely.