搜索

PythonReactSEOPDF
GitHub Skill

code-review

Reviews code changes with brief annotations. Use when user says "review code", "review changes", "what changed", "review pull request", "review PR", "review the pr", "review this pr", "review [name]'s pr", "review new pr", "review latest pr", "let's review", "review https://github.com/.../pull/123", or runs /code-review.

Wizard1209☆ 6 仓库 Stars1 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Code Review

Interactive guided tour through code changes.

Quick Start

# For PRs: get PR info and diff
gh pr list
gh pr view <number>
gh pr diff <number>

# For local changes
git diff HEAD --stat

Review Protocol

1. Overview (2-3 sentences max)

What the PR/changes accomplish at high level.

2. Offer Branch Switch

For PRs, offer to checkout the branch so user can explore in IDE alongside.

3. Tour Map

Show grouped file list so user sees full scope:

| Group        | Files                    |
| ------------ | ------------------------ |
| Core feature | `main.py`, `helper.py`   |
| Utilities    | `utils.py`, `config.py`  |
| Docs         | `README.md`, `CHANGELOG` |
4. File-by-File Tour

Walk through each changed file:

  • Brief description of what changed
  • At complex points: offer to trace execution flow
  • Batch small/related files into single stops (e.g., utils + related refactors)
  • End each stop clearly: "Questions, or next file?"
5. Flow Tracing (on-demand)

When user wants to understand a specific feature deeper, trace the execution path:

Entry point (e.g., handler receives message)
    ↓
Layer 2 (calls helper function)
    ↓
Layer 3 (calls API/database)
    ↓
Back up the stack with result

This shows how pieces connect across files.

6. Wrap-up

Quick summary of key changes when tour completes:

**PR Summary:**
- Main feature added
- Supporting changes
- Dependencies/config updates

Ready to merge, or any concerns?

Tour Stop Format

## [filename.py](path/to/file.py) (+X/-Y)

**What changed:**
• Change 1
• Change 2

**Key point:** [explanation of important logic]

→ Want to trace how [feature X] flows through the code?

Questions, or next file?

Guidelines

Include:

  • Functional changes (new logic, modified behavior)
  • Security-sensitive code
  • Breaking changes
  • New dependencies

Skip:

  • Import reordering
  • Formatting-only
  • Comment typos
  • Lock files, generated code

Scope Options

Scope Command
PR gh pr diff <number>
Uncommitted git diff HEAD
Staged only git diff --cached
vs main git diff main...HEAD
Last N commits git diff HEAD~N..HEAD

External PR URLs

When given a GitHub URL like https://github.com/owner/repo/pull/123:

  1. Parse owner, repo, and PR number from URL
  2. Use -R owner/repo flag for gh commands:
gh pr view 123 -R owner/repo --json title,body,author,state,additions,deletions,files,baseRefName,headRefName
gh pr diff 123 -R owner/repo
  1. Follow the standard review protocol above

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-01-26
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!