crlf-mechanical-formatting

Normalize Unreal Engine source files with CRLF line endings and indentation.

16|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill crlf-mechanical-formatting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crlf-mechanical-formatting
Source: https://github.com/OrionUE/Orion_FreeEdition/tree/main/.agents/skills/crlf-mechanical-formatting
Command: npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill crlf-mechanical-formatting

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents formatting automation from damaging Windows text files by preserving CRLF line endings, indentation conventions, and required project header formatting during bulk rewrites.

Core Features & Use Cases

  • CRLF Preservation: Normalizes text files with explicit Windows line endings and UTF-8 byte writing to avoid accidental LF-only output.
  • Mechanical Formatting Safety: Converts indentation patterns, protects copyright headers, and validates formatting workflows for Unreal Engine source and project files.
  • Use Case: Imagine updating many Unreal Engine C++ and configuration files at once. Use this Skill to apply consistent formatting while avoiding unwanted changes to third-party code, generated files, or project style requirements.

Quick Start

Use the crlf-mechanical-formatting skill to safely normalize the formatting of the Unreal Engine source files I modified while preserving CRLF line endings and project conventions.

Frequently Asked Questions about crlf-mechanical-formatting

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

FAQPage Schema
How do I preserve CRLF line endings when bulk formatting Unreal Engine source files?

To preserve CRLF line endings, you can apply mechanical formatting that explicitly normalizes Unreal Engine source files using Windows line endings and UTF-8 byte writing. This prevents accidental LF-only output during automated rewrites.

What is mechanical formatting safety for C++ and PowerShell files?

Mechanical formatting safety is the process of converting indentation patterns, protecting copyright headers, and validating workflows for C++ and PowerShell files. It ensures bulk rewrites do not damage Windows text formatting integrity or project style requirements.

Can I normalize indentation in Build.cs and Target.cs files without altering copyright headers?

Yes, you can normalize indentation in Build.cs and Target.cs files while protecting copyright headers. The formatting workflow explicitly safeguards required project header formatting and indentation conventions during bulk updates.

Does this formatting approach work with Unreal Engine plugin descriptors and XML project files?

Yes, this formatting approach works with Unreal Engine plugin descriptors, project files, and XML. It normalizes text files with explicit Windows line endings to avoid introducing incorrect line endings across various Unreal repository configurations.

Why does automated code formatting break Windows text files in Unreal repositories?

Automated code formatting breaks Windows text files when it introduces incorrect LF line endings or alters indentation conventions. Explicit CRLF writing and validation workflows are required to maintain formatting integrity for Windows environments.