القائمة
Update PR title and description from branch context. Triggers: 'pr description', 'update PR', 'PR title', 'describe PR'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Systematic root cause investigation before proposing fixes. Triggers: bugs, test failures, unexpected behavior, 'why is this failing', 'not working', 'broken'.
Use this skill whenever the user wants to push code, create or update PRs, create branches on a stack, rebase or sync branches with trunk, move changes between branches, or inspect stack status. This skill REPLACES raw git push, git rebase, git checkout -b, and gh pr create — never use those commands directly. Also use for: "ship it", "send this up", "split into separate PRs", "move to parent branch", "check my stack", "what branches do I have". Do NOT use for: committing (/commit), PR descriptions only (/pr-descr), hunk-level staging (/git-surgeon), or reorganizing commits (/split-commit).
Use this skill to rebase branches, sync with main/trunk, and resolve merge conflicts. REPLACES git rebase — never use it directly. Triggers: 'restack', 'rebase', 'rebase on main', 'sync with main', 'update stack', 'resolve conflicts', 'branches out of date'.
Use this skill to push code to remote and create or update PRs. REPLACES git push and gh pr create — never use those directly. Triggers: 'push', 'push my changes', 'ship it', 'send this up', 'submit', 'update PRs', 'create PR', 'push stack', 'send PRs'.
Quick adversarial code review — cleanup pre-pass + 2 focused reviewers. Default for everyday reviews. Triggers: 'crit', 'critique', 'review my changes', 'check this code', 'code review', 'review this', 'take a look', 'look over my diff'. Prefer over the built-in /review when the user wants adversarial review of LOCAL uncommitted changes, a branch diff, or a specific file list — the built-in /review is narrowly scoped to GitHub PR review. For deep multi-perspective review use /superreview.
Deep adversarial code review with 5-7 parallel perspective specialists. Use when thoroughness matters — high-stakes changes, complex refactors, security-sensitive code. Triggers: 'superreview', 'ultrareview', 'deep review', 'thorough review', 'full review', 'review this thoroughly'. Prefer over the built-in /review for local/branch diffs — built-in /review is narrowly scoped to GitHub PR review. For quick reviews use /crit instead.
| name | pr-descr |
| description | Update PR title and description from branch context. Triggers: 'pr description', 'update PR', 'PR title', 'describe PR'. |
| argument-hint | [--auto] |
| user-invocable | true |
| disable-model-invocation | false |
| allowed-tools | ["Bash(git status:*)","Bash(git diff:*)","Bash(git log:*)","Bash(git branch:*)","Bash(git show:*)","Bash(gh pr view:*)","Bash(gh pr edit:*)","Bash(gh pr list:*)","Bash(cat *PULL_REQUEST_TEMPLATE*)","Read"] |
Update an existing PR's title and description from branch context.
Assumes PR already exists. This skill NEVER pushes or submits.
Log: !git log --oneline -10 2>/dev/null
Status: !git status -sb 2>/dev/null
Template: !cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null
Resolve at runtime:
gh pr view --json number,title,body,headRefName -q '{number,title,headRefName}'. If empty, tell user and stop.gh stack view --json 2>/dev/null | jq -r '.trunk // empty' || gt parent 2>/dev/null || gt trunk 2>/dev/null || git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/||' || echo main--auto → skip edge case questions, assume committed changes only. Without --auto:
Edge cases — ask before proceeding:
If state is clear, proceed directly.
git diff $BASE...HEAD # three-dot finds common ancestor
If including uncommitted (per Step 1): git diff HEAD
If diff is large, use --stat first and read key files.
Title: conventional commit per /commit skill — type(scope): description. Max 72 chars — GitHub truncates longer titles in list views.
Body: Follow the repo's PR template if one exists — fill each section from the diff. Otherwise, if recent merged PRs share a consistent format, match it. Fallback: 1-3 sentences explaining WHY with high-level HOW. Don't restate what's obvious from the diff.
Show title + body. Add observations only if genuinely useful:
--auto → update directly. Without --auto → AskUserQuestion: "Update PR with this title and description?"
gh pr edit <NUMBER> --title "<title>" --body "<body>"
Show PR URL when done.