القائمة
Review ONNX Runtime pull requests, branches, commits, patches, and working-tree changes for actionable findings and missing tests.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/microsoft/onnxruntime --skill code-reviewيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Trigger, re-run, and unblock ONNX Runtime CI checks on a GitHub pull request. Use this skill when a required check is stuck, missing, failed, or needs re-running. Nearly all ORT CI runs as GitHub Actions workflows; only the "Linux Android Emulator QNN CI Pipeline" remains on Azure Pipelines, plus the bot-driven "license/cla" and "Python format" lint checks. Triggers on: rerun CI, retrigger checks, stuck check, missing pipeline, failed CI, license/cla, Python format failure, Doc Gen CI failure, operator docs out of date, /azp run.
Draft ONNX Runtime release notes using preset configurations for full ORT or scoped component releases. Use when generating highlights with PR links, compiling human contributor acknowledgments from compile_contributors.py output, and applying preset path filtering.
Audit and fix out-of-range output writes in ONNX Runtime operator shape-inference functions. Use when reviewing or fixing a contrib (or standard) op TypeAndShapeInference where a getNumOutputs() guard precedes a write to a higher output index - optional trailing outputs make a smaller output count schema-valid, so getOutputType(index) can run one past the declared outputs at Graph::Resolve.
| name | code-review |
| description | Review ONNX Runtime pull requests, branches, commits, patches, and working-tree changes for actionable findings and missing tests. |
Use this workflow for code review.
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.
Review the diff in context, including controlling code, relevant callers, and affected tests. Trace inputs through the changed behavior to externally visible results or failure modes.
Distinguish defects introduced by the change from pre-existing issues.
Ensure coverage of all the following:
Also report actionable clarity and maintainability concerns, even when they are not correctness defects.
Do not report formatting issues already enforced by repository tooling.
Report each actionable finding separately, using an inline comment when supported. Each finding must include:
If no actionable findings are found, say so explicitly.