Add a domain-specific Continue check example for Unity/C#

[danyalahmed1995]

Hey, I’m interested in contributing a small docs example for Continue checks.

I work mostly with Unity/C# projects, and I was thinking it could be useful to add an example check that shows how teams can write more domain-specific review prompts instead of only generic code review prompts.

For example, a Unity/C# check could look for things like:

• MonoBehaviour lifecycle issues
• missing serialized field validation / null reference risks
• coroutine or async callbacks touching destroyed objects
• expensive calls inside Update/FixedUpdate
• Resources or StreamingAssets path mistakes
• platform guards like UNITY_ANDROID / UNITY_IOS / UNITY_EDITOR

I’m not suggesting any Unity specific product support. I’m thinking of this more as a docs-only example that shows how checks can be adapted to a specific framework or codebase.

Would something like this be useful in the docs?

If yes, I can open a small PR with a concise example check and place it wherever maintainers think it fits best.