Reviewing ONNX Runtime Code Changes

Use this workflow for code review.

1. Establish the review scope

Determine the review base before analyzing the change. Identify the exact commits or working-tree state being reviewed, then enumerate all changed files.

If no changed files are found, respond with: "No changes detected. Please specify a commit range, branch, or patch to review."

Read every .github/instructions/**/*.instructions.md file whose applyTo scope matches a changed path. Also load each domain skill whose description matches the changed subsystem or behavior.

If no instructions file or domain skill matches a changed path, proceed using general ONNX Runtime and language-specific conventions.

2. Analyze changed behavior