pr PR审查

Name: pr PR审查
Author: tomevault-io

工程开发社区

作者仓库星标 0
作者仓库 skills-registry

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

方法与流程

Workflow：原文以此为独立章节。
Step 1: Check branch：Run git branch --show-current. If on main, tell the user they cannot create a PR from the main branch and stop. Run git log main..HEAD --oneline to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there…
Step 2: Check working directory：Run git status to check if the working directory is clean. Clean: Proceed to Step 3. Dirty (any staged, unstaged, or untracked changes): Ask the user:

适用与边界

当前原文没有单列适用场景。
Rules：This skill only creates PRs. It does not format, stage, or commit code. The PR title must follow Conventional Commits pattern (e.g., feat:, fix:, refactor:). If a PR already exists for this branch, display the existing PR URL instead of creating a new one.

原文中的明确线索

要点：「Clean」、「Dirty」、「Run git branch --show-current.」、「Run git log main..HEAD --oneline to check for commits ahead of main.」、「Run git status to check if the working directory is clean.」、「- Clean: Proceed to Step 3.」、「1. Run git push -u origin HEAD to push the branch.」、「1. Run gh pr edit --add-reviewer @copilot to request Copilot code review.」
文件与命令：git branch --show-current、main、git log main..HEAD --oneline、git status、/ci、git push -u origin HEAD、git log main..HEAD、gh pr create

流狐整理：以上内容来自当前 SKILL.md 的章节与原词；未补写作者没有声明的工具、兼容性或能力。

Quick Reference

/pr                 # Create GitHub PR from current branch

Workflow

Step 1: Check branch

Run git branch --show-current. If on main, tell the user they cannot create a PR from the main branch and stop.

Run git log main..HEAD --oneline to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop.

Step 2: Check working directory

Run git status to check if the working directory is clean.

Clean: Proceed to Step 3.
Dirty (any staged, unstaged, or untracked changes): Ask the user:
1. Commit changes first — suggest using /ci, then stop and let the user run it.
2. Ignore local changes and continue creating the PR based on existing commits only.

Step 3: Push and create PR

Run git push -u origin HEAD to push the branch.
Run git log main..HEAD to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them.
Run gh pr create with a title following Conventional Commits pattern. Base branch is main.

Step 4: Request review agents

After the PR is created, automatically request code review from available review agents:

Run gh pr edit --add-reviewer @copilot to request Copilot code review.
If the command succeeds, note that Copilot review has been requested.
If it fails (e.g., Copilot not available for the repo), skip silently and continue.

Step 5: Show result

Display the PR URL to the user, along with the review request status.

Rules

This skill only creates PRs. It does not format, stage, or commit code.
The PR title must follow Conventional Commits pattern (e.g., feat:, fix:, refactor:).
If a PR already exists for this branch, display the existing PR URL instead of creating a new one.

Source: darknight/cc-deck — distributed by TomeVault.

流狐档案作者与许可取自来源；运行、权限和网络为流狐检测或估算

流狐分类: 工程开发
作者声明 Agent: 未找到明确声明；不据此推断已兼容或已测试
静态检查: 88 / 100 · 启发式扫描，不代表运行安全
作者 / 版本 / 许可: @tomevault-io · 未声明 license
流狐 Token 估算: 低消耗
流狐接入估算: 即装即用
是否需要外部 API Key: 未发现要求
检测到的系统要求: 未声明
底层运行要求: 未声明
检测到的文件与系统行为: 只读
允许写入 / 修改
检测到的网络行为: 仅限本地
安装命令数: 无（仅作为资料）

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 pr-tomevault-io.preview

# Step 5: Show result

Display the PR URL to the user, along with the review request status.

SKILL.md SKILL.md

## Quick Reference
```
/pr                 # Create GitHub PR from current branch
```

## Workflow

### Step 1: Check branch

Run `git branch --show-current`. If on `main`, tell the user they cannot create a PR from the main branch and stop.

Run `git log main..HEAD --oneline` to check for commits ahead of main. If there are no commits AND the working directory is clean, tell the user there is nothing to create a PR for and stop.

### Step 2: Check working directory

Run `git status` to check if the working directory is clean.

- **Clean**: Proceed to Step 3.
- **Dirty** (any staged, unstaged, or untracked changes): Ask the user:
  1. Commit changes first — suggest using `/ci`, then stop and let the user run it.
  2. Ignore local changes and continue creating the PR based on existing commits only.

### Step 3: Push and create PR

1. Run `git push -u origin HEAD` to push the branch.
2. Run `git log main..HEAD` to analyze all commits on this branch. Generate a succinct, self-explanatory PR description from them.
3. Run `gh pr create` with a title following `Conventional Commits` pattern. Base branch is `main`.

### Step 4: Request review agents

After the PR is created, automatically request code review from available review agents:

1. Run `gh pr edit --add-reviewer @copilot` to request Copilot code review.
2. If the command succeeds, note that Copilot review has been requested.
3. If it fails (e.g., Copilot not available for the repo), skip silently and continue.

### Step 5: Show result

Display the PR URL to the user, along with the review request status.

## Rules

- This skill only creates PRs. It does not format, stage, or commit code.
- The PR title must follow Conventional Commits pattern (e.g., `feat:`, `fix:`, `refactor:`).

…

证据边界与执行链路

作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。

章节    -> Quick Reference → Workflow → Step 1: Check branch → Step 2: Check working directory → Step 3: Push and create PR → Step 4: Request review agents
要点    -> Clean · Dirty · Run git branch --show-current. · Run git log main..HEAD --oneline to check for commits ahead of main. · Run git status to check if the working directory is clean. · - Clean: Proceed to Step 3. · 1. Run git push -u origin HEAD to push the branch. · 1. Run gh pr edit --add-reviewer @copilot to request Copilot code review.
文件/命令 -> git branch --show-current · main · git log main..HEAD --oneline · git status · /ci · git push -u origin HEAD · git log main..HEAD · gh pr create
内容 SHA-256 -> bad1917f37bf