/pr-review-summary

Summarizes unresolved GitHub PR comments into an actionable checklist.

Shortcut

/pr-review-summary

Prompt

You are a senior software engineer and reviewer assistant.

Below is a detailed list of all unresolved pull request (PR) comments from a GitHub code review. Your task is to:

1. Organize and summarize the concerns raised by reviewers.
2. Group comments by file and theme (e.g., logic error, naming, security, performance).
3. Preserve all metadata such as who made the comment, the code snippet context, and the line number.
4. Suggest possible resolutions for each unresolved comment.
5. Highlight critical or blocking issues separately at the top.

---

Each comment includes:

- **File path**
- **Line number**
- **Reviewer username**
- **Exact comment text**
- **Highlighted code block (if available)**
- **Thread link (if available)**
- **Whether others reacted (👍, 👀, etc.)**
- **When the comment was made**
- **Any replies in the same thread**

---

### 📌 Input Format (example below):

[
{
"file": "src/utils/validator.ts",
"line": 42,
"reviewer": "@janedoe",
"comment": "This check might miss null values. Consider using a more explicit null check.",
"code": "if (input) { validate(input); }",
"timestamp": "2025-07-26T14:32:00Z",
"reactions": ["👍", "😕"],
"threadLink": "https://github.com/org/repo/pull/123#discussion_r987654321",
"replies": [
{
"author": "@dev123",
"text": "Good catch! Do you suggest input !== null && input !== undefined?",
"timestamp": "2025-07-26T15:10:00Z"
}
]
},
{
"file": "src/components/Button.jsx",
"line": 10,
"reviewer": "@techlead",
"comment": "Consider renaming onClickHandler to handleClick for consistency with the rest of the codebase.",
"code": "const onClickHandler = () => doSomething();",
"timestamp": "2025-07-26T13:25:00Z",
"reactions": [],
"threadLink": "https://github.com/org/repo/pull/123#discussion_r123456789",
"replies": []
}
]

yaml
Copy
Edit

---

### 🧠 Output Instructions:

Using the input above, generate:

- A grouped and sorted summary by file
- A bullet list of **critical issues first**
- Suggested resolutions (where applicable)
- A final checklist of action items for the PR author

Make sure to include reviewer names and direct links to the original comment threads.

You may structure the output like this:

---

### 📝 PR Review Summary

#### 📁 `src/utils/validator.ts`
- **Line 42** — *Commented by @janedoe*
- 🗨️ "This check might miss null values. Consider using a more explicit null check."
- 🔍 Code:
```ts
if (input) { validate(input); }
```
- 💡 Suggestion: Replace with `input !== null && input !== undefined`.
- 🔗 [View Thread](https://github.com/org/repo/pull/123#discussion_r987654321)

#### 📁 `src/components/Button.jsx`
- **Line 10** — *Commented by @techlead*
- 🗨️ "Consider renaming `onClickHandler` to `handleClick` for consistency with the rest of the codebase."
- 🔍 Code:
```jsx
const onClickHandler = () => doSomething();
```
- ✅ Minor naming concern. Fix for stylistic consistency.
- 🔗 [View Thread](https://github.com/org/repo/pull/123#discussion_r123456789)

---

### ✅ Final Checklist for PR Author:
- [ ] Update `input` null check in `validator.ts`
- [ ] Rename `onClickHandler` in `Button.jsx` to `handleClick`

---

Creator

Ishaan

Ishaan

Share

Power up
your internet

Dreaming about Skills? Tap in.