Simple PR审查
- 作者仓库星标 15,240
- 许可证 MIT
- 作者仓库 tantivy
Simple PR
Follow these steps to create a simple PR from staged changes:
Step 1: Check workspace state
Run: git status
Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with git add.
Also verify that we are on the main branch. If not, abort and ask the user to switch to main first.
Step 2: Ensure main is up to date
Run: git pull origin main
This ensures we're working from the latest code.
Step 3: Review staged changes
Run: git diff --cached
Review the staged changes to understand what the PR will contain.
Step 4: Generate commit message
Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what".
Display the proposed commit message to the user and ask for confirmation before proceeding.
Step 5: Create a new branch
Get the git username: git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'
Create a short, descriptive branch name based on the changes (e.g., fix-typo-in-readme, add-retry-logic, update-deps).
Create and checkout the branch: git checkout -b {username}/{short-descriptive-name}
Step 6: Commit changes
Commit with the message from step 3:
git commit -m "{commit-message}"
Step 7: Push and open a PR
Push the branch and open a PR:
git push -u origin {branch-name}
gh pr create --title "{commit-message-title}" --body "{longer-description-if-needed}"
Report the PR URL to the user when complete.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @quickwit-oss · MIT
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Run: git status Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with git add. Also verify that we are on the main branch. If not, abort and ask the user to…
Run: git pull origin main This ensures we're working from the latest code.
Run: git diff --cached Review the staged changes to understand what the PR will contain.
Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what". Display the proposed commit message to the user and ask for confirmation before proceeding.
Get the git username: git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]' Create a short, descriptive branch name based on the changes (e.g., fix-typo-in-readme, add-retry-logic, update-deps). Create and checkout the branch: git checkout -b…
Commit with the message from step 3:
# Simple PR
Follow these steps to create a simple PR from staged changes:
## Step 1: Check workspace state
Run: `git status`
Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with `git add`.
Also verify that we are on the `main` branch. If not, abort and ask the user to switch to main first.
## Step 2: Ensure main is up to date
Run: `git pull origin main`
This ensures we're working from the latest code.
## Step 3: Review staged changes
Run: `git diff --cached`
Review the staged changes to understand what the PR will contain.
## Step 4: Generate commit message
Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what".
Display the proposed commit message to the user and ask for confirmation before proceeding.
## Step 5: Create a new branch
Get the git username: `git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'`
Create a short, descriptive branch name based on the changes (e.g., `fix-typo-in-readme`, `add-retry-logic`, `update-deps`).
Create and checkout the branch: `git checkout -b {username}/{short-descriptive-name}`
## Step 6: Commit changes
Commit with the message from step 3:
```
git commit -m "{commit-message}"
```
## Step 7: Push and open a PR
Push the branch and open a PR:
```
git push -u origin {branch-name}
gh pr create --title "{commit-message-title}" --body "{longer-description-if-needed}"
```
Report the PR URL to the user when complete. 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Step 1: Check workspace state → Step 2: Ensure main is up to date → Step 3: Review staged changes → Step 4: Generate commit message → Step 5: Create a new branch → Step 6: Commit changes
要点 -> Verify that all changes have been staged (no unstaged changes). · Also verify that we are on the main branch. · This ensures we're working from the latest code. · Review the staged changes to understand what the PR will contain. · Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what". · Display the proposed commit message to the user and ask for confirmation before proceeding. · Create a short, descriptive branch name based on the changes (e.g., fix-typo-in-readme, add-retry-logic, update-deps). · Report the PR URL to the user when complete.
文件/命令 -> git status · git add · main · git pull origin main · git diff --cached · git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]' · fix-typo-in-readme · add-retry-logic
内容 SHA-256 -> dfd8f06e36a6
方法与流程
适用与边界
原文中的明确线索
git status、git add、main、git pull origin main、git diff --cached、git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'、fix-typo-in-readme、add-retry-logic