Engineering
code-review-netsync avatar

code-review-netsync

Automated code review for STYLY-NetSync, enforcing protocol parity, thread safety, and Unity C#/Python conventions.

Introduction

The code-review-netsync skill is a specialized engineering tool designed for developers working on the STYLY-NetSync repository, a high-performance Unity networking framework for Location-Based Entertainment (LBE). It performs automated code reviews by analyzing git diffs against a rigorous set of project-specific rules, ensuring code quality and synchronization between the Unity (C#) client and the Python-based server. This skill is intended for software engineers and technical artists preparing code for merge requests or deployment in venue-based XR environments.

  • Performs automated validation of git diffs against Unity C# and Python coding standards, including null safety, thread safety for UnityEngine APIs, and proper ZeroMQ pattern usage.

  • Monitors and flags protocol changes by detecting modifications to serialization logic, protocol constants (like MSG_CLIENT_POSE or PROTOCOL_VERSION), and quantization settings.

  • Ensures cross-language parity, flagging instances where changes in Unity C# classes (e.g., NetSyncManager, BinarySerializer) lack corresponding updates in Python files (e.g., client.py, binary_serializer.py).

  • Enforces strict adherence to project architecture, such as the avoidance of ZMQ_CONFLATE, correct handling of multi-part messages, and ensuring documentation is maintained in English.

  • Categorizes findings by severity (CRITICAL, WARNING, INFO) with actionable suggestions for remediation.

  • Use this skill when submitting pull requests or modifying core networking components to catch bugs, protocol mismatches, or thread safety issues before they reach production.

  • The tool requires a git diff as input (unstaged, staged, or range-based) to identify target files.

  • If protocol trigger files like BinarySerializer.cs or types.py are modified, the skill automatically applies a comprehensive protocol impact checklist.

  • Always review the 'CRITICAL' output before merging, as these flags address potential crashes or corruption in the LBE networking stack.

Repository Stats

Stars
38
Forks
10
Open Issues
13
Language
Python
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 10:37 PM
View on GitHub