القائمة
Use to validate XppAI outputs before final delivery, especially to enforce Tag ID block compliance and ensure no edits are proposed inside localization blocks (<GBR>, <GIN>, <GJP>, <GSA>, <GTH>).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when analyzing X++ AX 2009 profiler traces, code stack traces, or execution paths to identify performance bottlenecks — repeated call chains, quadratic loops, expensive constructor+calc combos, excessive tax/totals recalculation, or deep framework cascades.
Use when reviewing X++ or general ERP source code for architectural weaknesses, design gaps, fragile sequencing, responsibility mismatches, technical debt, or structural risks — not just syntax or performance issues.
Use when given any X++ AX 2009 artifact — stack trace, method, class, form XPO, posting code, or table — and you need a full structured multi-skill analysis applied automatically based on artifact type.
Use when proposing X++ AX 2009 code fixes for identified performance bottlenecks or behavioral bugs — minimal, production-safe changes that preserve business logic and fit ERP team review standards.
Use for all XppAI AX 2009 tasks as the canonical core baseline (architecture, language, lifecycle, hard constraints, and evidence labels).
Use when deep AX 2009 analysis is required (performance, posting, totals/tax, framework patterns, customization safety, and architecture judgment).
استنادا إلى تصنيف SOC المهني
| name | xppai-review |
| description | Use to validate XppAI outputs before final delivery, especially to enforce Tag ID block compliance and ensure no edits are proposed inside localization blocks (<GBR>, <GIN>, <GJP>, <GSA>, <GTH>). |
Run this as a final gate before returning fix/review/report output.
//<TagId - ProjectId - DD/MM/YYYY - DevName>//</TagId - ProjectId - DD/MM/YYYY - DevName>Tag ID, Project ID, Dev Name, date.DD/MM/YYYY.<GBR>, <GIN>, <GJP>, <GSA>, <GTH> (including comment-style tag variants).Return only:
Review result: PASS|FAIL
Failed checks: <comma-separated rule ids or "none">
Required corrections: <short imperative list or "none">
TAG-1: Missing tag block markersTAG-2: Missing Tag ID / Project ID / Dev Name / dateTAG-3: Invalid date format for tagLOC-1: Proposed edit inside localization blockAX-1: Non-AX2009 pattern in fix snippetAX-2: Variable declarations not at topDOC-1: Missing assumptions when requiredIf Review result: FAIL, upstream orchestrator must revise and re-run this review once before finalizing output.