burst-safety

Enforce Burst safety rules for Unity DOTS job code.

6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/dyCuong03/unity-agent-team --skill burst-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burst-safety
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/burst-safety
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill burst-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Burst compilation and runtime can fail or silently degrade when DOTS systems jobs accidentally use managed types, reflection, logging, or unsafe patterns inside Burst-compiled code paths.

Core Features & Use Cases

  • Burst-safe code rules for DOTS/Hybrid: Enforces hard constraints for what may appear inside [BurstCompile] methods and jobs.
  • Pre-verifier diagnostic checklist: Provides a concrete checklist to validate Burst compatibility before handing off to verification.
  • Prevents common Burst failure modes: Targets frequent issues like BC1015 static evaluation failures, managed wrapper usage (e.g., Mathf/Vector3), and forbidden exceptions/debugging.

Quick Start

Use the burst-safety skill pack when triage classifies the task as domain=DOTS|Hybrid, then apply its rules to every touched system or job before signaling the verifier.

Frequently Asked Questions about burst-safety

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

FAQPage Schema
Why does my Unity DOTS Burst compilation fail with BC1015 static evaluation errors?

Burst compilation fails when DOTS jobs use managed types, reflection, logging, or unsafe patterns inside [BurstCompile] methods. Enforcing strict Burst safety rules prevents these invalid non-Burst-compatible patterns from failing or silently degrading compilation.

How do I enforce Burst-safe code rules for Unity DOTS job systems?

To enforce Burst-safe code for DOTS job systems, apply strict constraints to every touched [BurstCompile] system or job. This prevents forbidden managed wrappers, virtual dispatch, and math API usage before signaling the verifier for compilation readiness.

Can I use managed wrappers like Mathf and Vector3 inside Burst-compiled code?

No, using managed wrappers like Mathf and Vector3 inside Burst-compiled code causes failures. You must satisfy managed-type and math API constraints by replacing them with Burst-compatible alternatives to prevent silent runtime degradation.

What is a pre-verifier diagnostic checklist for Unity Burst compatibility?

A pre-verifier diagnostic checklist for Unity Burst compatibility is a validation step ensuring DOTS systems and jobs meet hard constraints before compilation. It checks for managed types, reflection, logging, and forbidden exceptions to guarantee artifact validation readiness.

When do I need to run Burst safety checks on Hybrid DOTS systems?

You need to run Burst safety checks on Hybrid DOTS systems when triage classifies the task as DOTS or Hybrid and involves [BurstCompile] systems and jobs. This ensures strict safety rules are applied before handing off to verification.