agentleFS
SentryKnown publishergetsentry/sentry-unreal/.claude/skills/ue-build/SKILL.md

ue-build

Skill177 starsChanged 4 days agoMITView on GitHub

Build the SentryPlayground sample project for a target platform

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. GuangminJu/UnrealSkills★ 12same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the UNREAL_ENGINE_ROOT environment variable (use PowerShell .NET method on Windows: …

    line 8
  2. Very specific:

    Full package: - when the user wants a packaged, runnable game build (e.g.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build the SentryPlayground sample project.

  1. Check the UNREAL_ENGINE_ROOT environment variable (use PowerShell .NET method on Windows: [System.Environment]::GetEnvironmentVariable('UNREAL_ENGINE_ROOT')). If unset or the path doesn't exist, ask the user for the engine path.
  2. Choose the build mode from conversation context:

    • Compile-only (default) - when the goal is verifying that code compiles after changes, or as a prerequisite for /ue-unit-test. Invokes UnrealBuildTool directly and is much faster than a full package.
    • Full package - when the user wants a packaged, runnable game build (e.g. as a prerequisite for /ue-integration-test, or if they mention packaging/cooking/distribution).
  3. Determine the target platform from conversation context using this lookup table. If no platform is mentioned, default to the host platform (Win64 on Windows, Mac on macOS, Linux on Linux). If ambiguous, ask the user.

    AliasPlatform flag
    Win64, WindowsWin64
    Mac, macOSMac
    AndroidAndroid
    iOSIOS
    LinuxLinux
    LinuxArm64LinuxArm64
    XSX, Xbox SeriesXSX
    XB1, Xbox OneXB1
    PS5, PlayStationPS5
    Switch, NXSwitch
  4. Determine the build configuration: use Development by default, or Shipping if the user mentions it.

Compile-only build

Resolve the repo root and invoke UnrealBuildTool with the editor target for the host platform:

REPO=$(git rev-parse --show-toplevel)

# Windows
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/Build.bat" SentryPlaygroundEditor Win64 Development \
    -project="$REPO/sample/SentryPlayground.uproject" -waitmutex

# macOS
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/Mac/Build.sh" SentryPlaygroundEditor Mac Development \
    -project="$REPO/sample/SentryPlayground.uproject" -waitmutex

# Linux
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/Linux/Build.sh" SentryPlaygroundEditor Linux Development \
    -project="$REPO/sample/SentryPlayground.uproject" -waitmutex

To compile-check a non-host or non-editor platform (e.g. Android, iOS, consoles), build the game target instead, substituting the platform and configuration: SentryPlayground <Platform> <Config>.

Full package build

Resolve the repo root and run the BuildCookRun command:

REPO=$(git rev-parse --show-toplevel)

# Windows
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/RunUAT.bat" BuildCookRun \
    -project="$REPO/sample/SentryPlayground.uproject" \
    -archivedirectory="$REPO/sample/dist" \
    -platform=Win64 -clientconfig=Development \
    -build -cook -stage -package -archive -nop4

# macOS
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/RunUAT.sh" BuildCookRun \
    -project="$REPO/sample/SentryPlayground.uproject" \
    -archivedirectory="$REPO/sample/dist" \
    -platform=Mac -clientconfig=Development \
    -build -cook -stage -package -archive -nop4

# Linux
"$UNREAL_ENGINE_ROOT/Engine/Build/BatchFiles/RunUAT.sh" BuildCookRun \
    -project="$REPO/sample/SentryPlayground.uproject" \
    -archivedirectory="$REPO/sample/dist" \
    -platform=Linux -clientconfig=Development \
    -build -cook -stage -package -archive -nop4

Substitute the platform and config values as determined above.

For Android Shipping builds, add the -distribution flag.

Execution notes

  • Builds regularly take longer than the default command timeout. Run the build command in the background and monitor its output, or raise the timeout accordingly.
  • On failure, check the logs for the root cause:
    • UnrealBuildTool: $UNREAL_ENGINE_ROOT/Engine/Programs/UnrealBuildTool/Log.txt
    • UAT (BuildCookRun): $UNREAL_ENGINE_ROOT/Engine/Programs/AutomationTool/Saved/Logs/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.