Skip to content
Skills Library
Programming · Testing

unity-build-validation

/unity-build-validation

Use when the task is to validate builds across target platforms with reproducible settings.

Licence
Apache-2.0
Last repository change
07.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when the task is to validate builds across target platforms with reproducible settings.

Original author description

Use when the task is to validate builds across target platforms with reproducible settings.

How it works

  1. Outcome
  2. Inputs and prerequisites
  3. Procedure
  4. Quality gates
  5. Deliverable
  6. Boundaries
Original SKILL.md headings · 40 lines, 323 words
SKILL.md preview
---
name: unity-build-validation
description: Use when the task is to validate builds across target platforms with reproducible settings.
license: Apache-2.0
---

# Unity Build Validation

## Outcome

Validate builds across target platforms with reproducible settings. The result must be traceable to supplied inputs and pass the checks below.

## Inputs and prerequisites

- Project version, target platform, render pipeline, plugin/package set, asset specifications, and acceptance criteria.
- The target Unity Editor version, required platform build modules, Unity Package Manager dependencies, supported scripting APIs, profilers, and Editor.log.
- Confirm the target application's version and the actual capabilities available in this environment.

## Procedure

1. Inspect project version, target platform, render pipeline, plugins/packages, and existing conventions.
2. Import assets into a dedicated staging location with correct units, pivots, materials, collisions, and LODs.
3. Use engine-native systems and keep generated assets separate from hand-authored source content.
4. Profile the target scene/build; do not optimize from visual guesswork or editor-only timing.
5. Build from a clean state and inspect logs, missing references, shader compilation, and startup behavior.
6. Test on the intended platform or report the exact platform that was not available.

## Quality gates

- A successful editor import does not prove a package build works.
- Do not change project-wide rendering or package versions without a scoped impact review.
- Performance claims require a captured baseline and comparable test conditions.

## Deliverable

Engine project changes, imported asset manifest, build/profile evidence, and platform-specific limitations. Include the exact commands or application operations used, the files changed, and the checks that were actually run.

## Boundaries

- Keep source files unchanged; write new versions to an explicit output path.
- Do not transmit private assets or prompts to an external provider unless the user has explicitly approved that destination.
- Do not run paid generation or destructive application operations without clear authorization and a stated budget or scope.
- If a required application, plugin, model, or entitlement is absent, report the limitation and stop at the last verified stage.
- Separate measured results from visual judgment, assumptions, and recommendations.

Versions

The database has no other skills named unity-build-validation.

Database snapshot: 13.11.2026 · package version f5d2b779a9e9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90unity-project-audit
    Use when the task is to inspect Unity project settings, packages, scenes, and build targets.
  • 90unity-build
    Generate and validate Unity 2022.3 LTS projects on this VM. Use when the user asks for Unity C# code, a Unity project, or a headless Unity build. Owns the C# scaffolds, project skeleton, and batchmode verification.
  • 100unity-dev
    Use when implementing a Unity C# feature or fix, or when the user requests Unity architecture, implementation, review, or tests.
  • 100unity-build-platforms
    Unity builds — IL2CPP vs Mono, build profiles, addressables-aware builds, Android (Gradle, AAB, Play Asset Delivery), iOS (Xcode post-processing, capabilities), WebGL, console NDA paths (high-level only). USE WHEN: configuring build settings, fixing platform-specific issues,…
  • 100unity-run
    Use when running Unity from CLI for any purpose — builds, tests, method execution, asset imports. Handles Unity installation detection, batchmode execution, and log monitoring. Other unity-dev skills depend on this for CLI execution.
  • 100unity-scene
    シーン構築ワークフロー。オブジェクト配置、コンポーネント設定、Prefab化、シーン保存。 Use for: "シーン構築", "オブジェクト配置", "Prefab化", "コンポーネント設定

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.