checking-torquescript-conventions

name	checking-torquescript-conventions
description	Use when reviewing or verifying changed TorqueScript (.cs) files against the project's coding conventions — after editing or adding game/UI scripts, before committing or opening a PR, or whenever asked to check that script code conforms to TORQUE_SCRIPT.md.

Checking TorqueScript conventions

Overview

Verify that the .cs script files changed on this branch follow the project's TorqueScript conventions. The rules live in TORQUE_SCRIPT.md at the repo root — that file is the source of truth; this skill is the review procedure. Read the doc; don't check from memory (it evolves).

Steps

1. List the changed .cs files. Default scope = everything this branch changed, committed or not:

   git status --porcelain -- '*.cs'                 # uncommitted: modified (M), staged, untracked (??)
   git diff --name-only <base>...HEAD -- '*.cs'      # committed on this branch (<base> = development/master/main)
   

   Review the union, deduped. Skip deleted (D) files. The conventions target game/UI module scripts — don't audit vendored engine code or unrelated sample toys unless those are what changed. State which scope you used.

2. Read TORQUE_SCRIPT.md. Use its rules + checklist as the criteria.

3. Check each file against the checklist (below).

4. Report per-file: conforms, or list each violation with the file, the rule it breaks, and a file:line. End with a one-line summary.