unity-compile-fixer_skill

Overview

This skill detects and resolves Unity C# compilation errors by reading VSCode (OmniSharp) diagnostics and proposing context-aware fixes. It matches error codes against a curated pattern database, generates minimal edits, and helps manage version control concerns like .meta conflicts. Use it to speed up diagnosis and safely apply fixes with user approval.

How this skill works

The skill collects diagnostics via the IDE diagnostics tool and filters for OmniSharp C# errors (severity: Error, CS* codes). It loads an error-pattern database, examines the file context where each error occurs, and builds structured fix proposals. After user confirmation, it applies minimal edits, preserves formatting, checks VCS status (including .meta files), and re-runs diagnostics to verify results.

When to use it

• Unity projects showing C# compiler errors in VSCode (OmniSharp) that need diagnosis
• When you want automated suggestions for CS* error codes (e.g., CS0246, CS1061)
• When working with version-controlled Unity projects that may have .meta conflicts
• When you prefer guided, minimal edits with explicit user approval before changes

Best practices

• Run full-project diagnostics first to capture dependent errors and priorities
• Fix foundational errors (missing using directives, undefined types) before downstream errors
• Batch related fixes in the same file to minimize churn and keep diffs small
• Always review proposed edits and confirm before applying changes
• Check .meta files and VCS status after edits to avoid asset GUID mismatches

Example use cases

• Add a missing using directive when Unity API types are unrecognized (e.g., Rigidbody)
• Fix type mismatches or incorrect method signatures flagged by CS0029 or CS1061
• Resolve namespace or assembly reference errors by suggesting imports or assembly updates
• Detect and report .meta file merge conflicts after automated script edits
• Re-validate diagnostics to show a before/after summary of fixed and remaining errors