القائمة
Generate the PR title and description from the current branch changes, following the repo's PR template.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/azerothcore/azerothcore-wotlk --skill generate-pr-descriptionيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | generate-pr-description |
| description | Generate the PR title and description from the current branch changes, following the repo's PR template. |
| metadata | {"version":"1.0"} |
Produce a copy-pasteable PR title and body for the current changes, based on the repo's
pull_request_template.md. Output text only — never create the PR, push, or run any
state-changing git command.
If a use-conversational-language skill is available, invoke it and follow it when writing the
prose. If not available, fetch it from its remote source.
"The changes" is the union of:
git diff <master-ref>...HEAD, where <master-ref> is origin/master —
or upstream/master when the checkout is a fork with an upstream remote;If all three are empty, say so and stop.
Only two sources may fill the description: the diff and facts stated in the conversation. Never present anything else as fact — no assumed testing, sources, issue links, or TODOs. A section without backing facts stays empty/unchecked, silently: an empty section is correct, a guessed one is wrong.
Ask the user only when unsure about substance — what the change does, which scope the title should carry, contradictory information. Missing fill-in facts are never a reason to ask.
type(Scope/Subscope): short description — imperative, max 50 chars. Types: feat, fix,
refactor, style, docs, test, chore; scopes: Core, Scripts, DB. Copy subscope naming
from recent commits touching the same areas (git log --oneline -- <paths>).
Fill in pull_request_template.md (repo root):
<!-- --> comments; keep the "How to Test AzerothCore PRs" footer
intact.src/server/scripts/ → Scripts; data/sql/ →
Database; other src/ → Core.Print exactly:
TITLE: <title>
PR DESCRIPTION:
```markdown
<body>
```