القائمة
Open or update a GitHub PR — reads the actual template at runtime, auto-detects create vs update mode, reconstructs body section-by-section
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/andrem-sec/psc-comet --skill github-prيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | github-pr |
| description | Open or update a GitHub PR — reads the actual template at runtime, auto-detects create vs update mode, reconstructs body section-by-section |
A pull request creation and update protocol that reads the project's actual PR template at runtime, auto-detects whether to open or update, and for updates modifies only the requested sections without touching the rest. The template is always the source of truth.
Without a protocol, PR bodies are written from memory: sections are guessed, some are skipped, and the title format is inconsistent. On updates, the entire body is replaced instead of surgically editing one section, which clobbers concurrent edits.
The auto-detect mode fix is equally important: when a PR already exists, the user usually wants to update it, not open a second one. Defaulting to Open when a PR exists is the wrong default.
Check for an open PR on the current branch:
gh pr view --json number,title,state 2>/dev/null
If an open PR exists and the user did not say "open a new PR" or "create a new PR": use Update mode. Otherwise: use Open mode.
Read .github/pull_request_template.md before doing anything else in either mode. Parse its ## section headers, required fields, and field markers. Never assume or hardcode section names.
Run in parallel:
git branch --show-current
git log origin/HEAD..HEAD --oneline
git diff origin/HEAD...HEAD --stat
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
Review changed files and commit messages to understand the nature of the change.
Draft a complete PR body using the parsed template structure:
feat(scope): description or fix(scope): description## PR Draft: <title>
Branch: <head> -> <base>
Labels: <suggested>
<full body>
Ask: "Review this draft: let me know what to change, or say 'submit' to open it." Iterate until approved.
If the branch is not yet pushed:
git push -u origin <branch>
Create the PR:
gh pr create --title "<title>" --base <base> --body "$(cat <<'PR_BODY_EOF'
<full body>
PR_BODY_EOF
)"
Add agreed labels:
gh pr edit <number> --add-label "<label1>,<label2>"
Return the PR URL.
Auto-detect from current branch:
gh pr view --json number,title,body,labels,state,author,url,headRefName 2>/dev/null
Verify the current user is the PR author:
gh api user --jq '.login'
If not the author: stop and inform the user. Do not edit a PR you did not open.
## PR #<number>: <title>
State: <open/closed/merged>
Branch: <head> -> <base>
Labels: <labels>
Checks: <pass/fail/pending>
URL: <url>
Supported operations:
| Operation | Command |
|---|---|
| Edit title | gh pr edit <n> --title "<title>" |
| Add labels | gh pr edit <n> --add-label "<label>" |
| Remove labels | gh pr edit <n> --remove-label "<label>" |
| Add comment | gh pr comment <n> --body "<text>" |
| Edit a section | Parse body by ## headers, modify target section only, reconstruct full body |
| Sync after new commits | Re-analyze diff, propose stale section updates, confirm before applying |
For any body edit: always fetch the latest body before editing to avoid overwriting concurrent changes. Parse by ## headers, modify only the requested section, reconstruct the full body:
gh pr edit <number> --body "$(cat <<'PR_BODY_EOF'
<full updated body>
PR_BODY_EOF
)"
gh pr view <number> --json number,title,labels,url
Return the PR URL.
Do not hardcode section names. Read the template file every time: it is the source of truth, not memory.
Do not replace the entire PR body to edit one section. Parse by headers, change the section, reconstruct. Everything else stays exactly as it was.
Do not edit a PR without verifying authorship. Editing someone else's PR body without their knowledge is a collaboration anti-pattern.
Do not use labels that do not exist in the repository. Run gh label list to verify.
Do not include sensitive data (tokens, keys, internal hostnames) in PR content.