pull-request

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Usage

使用方法

/pull-request [issue_number]

/pull-request [issue_number]

Arguments

参数

```
issue_number
```
(optional): 関連するGitHub Issue番号

```
issue_number
```
（可选）：关联的GitHub Issue编号

Dependencies

依赖项

use git-operations-specialist skill

使用git-operations-specialist skill

Your task

你的任务

IMPORTANT: Do exactly what is instructed below, nothing more, nothing less. Do not add any additional "helpful" behavior like checking for unstaged changes or suggesting to push first.

Delegate all operations to the git-operations-specialist skill:

ask the skill to check if a pull request already exists for current branch
- Use command:
```
gh pr list --head $(git branch --show-current) --state open --json number,title
```
if existing PR found:
- ask the skill to update the existing pull request with current branch changes
- update PR title and description based on latest commits
- preserve the existing PR description structure as much as possible
- if issue_number argument is provided, add "Related: #<issue_number>" to the description
if no existing PR found:
- ask the skill to create a new pull request with current branch
- if issue_number argument is provided, add "Related: #<issue_number>" to the description

重要提示：严格按照以下指示执行，不多做也不少做。不要添加任何额外的“辅助”操作，比如检查未暂存的更改或建议先推送代码。

将所有操作委托给git-operations-specialist skill：

让该skill检查当前分支是否已存在拉取请求

使用命令：

gh pr list --head $(git branch --show-current) --state open --json number,title

如果找到现有PR：
- 让该skill使用当前分支的更改更新现有拉取请求
- 根据最新提交更新PR标题和描述
- 尽可能保留现有PR描述的结构
- 如果提供了issue_number参数，在描述中添加“Related: #<issue_number>”
如果未找到现有PR：
- 让该skill为当前分支创建新的拉取请求
- 如果提供了issue_number参数，在描述中添加“Related: #<issue_number>”

Constraints

约束条件

Do NOT check git status or suggest pushing changes first
Do NOT display messages about unstaged changes
Do NOT add any preparatory steps beyond the specified tasks
Proceed directly with PR creation/update regardless of repository state

不要检查git状态或建议先推送更改
不要显示有关未暂存更改的消息
不要添加指定任务之外的任何准备步骤
无论仓库状态如何，直接进行PR创建/更新操作