القائمة
Update the current PR description based on commits vs main. Writes a concise summary, entrypoint, and details section.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/griddynamics/specflow --skill pr-descيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | pr-desc |
| description | Update the current PR description based on commits vs main. Writes a concise summary, entrypoint, and details section. |
| argument-hint | [optional context or focus area] |
git log main..HEAD --oneline to see commits on this branch.git diff main...HEAD --stat to see which files changed.gh pr view --json number,title,body to get the current PR (if one exists).gh pr edit --body "...".Separate using newlines only.
## Summary
<1-2 sentences: what this PR does and why>
## Entrypoint
<1-2 sentences: where a reviewer should start — the main hook-up point, the top-level call, the route/handler/config that ties it all together>
## Diagram
<If any flow or structure was changed, put the diagram here or reference a file with diagrams if that is used to track it by design.>
## Details
<Only non-obvious things: surprising design choices, edge cases, workarounds, things that look wrong but aren't. Skip plumbing, boilerplate, and straightforward wiring.>
Create well-structured git commits with clear, conventional commit messages. Use this skill whenever the user asks to commit changes, "commit this", "save my work", "make a commit", "write a commit message", or after completing a coding task when changes need to be committed. Also use when the user asks to split changes into multiple commits, amend a commit, or improve an existing commit message.
After substantive edits under backend/app, run static checks and optional Radon complexity (matches Makefile and Cursor post-write hook intent).
Generate a customer-specific deployment requirements document from the template. Takes customer name and known infrastructure details as input. Produces a filled-in requirements spec ready for human review before sending to the customer.
استنادا إلى تصنيف SOC المهني
