github-pr-review-fix

Featured

Review and resolve PR comments from GitHub. Validates each comment, fixes legitimate issues.

AI & Automation 3,698 stars 333 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Review PR Comments Review unresolved comments on the GitHub pull request associated with the current branch. Validate each comment, then fix legitimate issues. ## Step 1 — Identify the Pull Request 1. If `$ARGUMENTS` contains a PR number, use it. 2. Otherwise, detect the current git branch and find its open PR: ```bash gh pr view --json number,url,headRefName,baseRefName ``` 3. If no PR is found, stop and tell the user. ## Step 2 — Fetch All Unresolved Review Comments Fetch PR review comments (not issue-level comments) using the GitHub CLI: ```bash gh api repos/{owner}/{repo}/pulls/{number}/comments --paginate ``` Filter to comments where the thread is **not resolved**. Group comments by thread (same `in_reply_to_id` or same `path` + `line`/`original_line`). For each thread, treat the **first comment** as the review request and subsequent comments as discussion. Also fetch general PR comments (issue-level): ```bash gh api repos/{owner}/{repo}/issues/{number}/comments --paginate ``` If there are zero unresolved comments, report that and stop. ## Step 3 — Validate and Fix Comments in Parallel (Sub-agents) For **each** unresolved comment or comment thread, spawn a **sub-agent** in parallel. Use `model: "sonnet"` for cost efficiency. Each agent validates the comment and, if legitimate, fixes it immediately in place. **Conflict avoidance**: If multiple comments target the **same file**, run those agents **sequentially** (not in parallel) to avoid edit confli...

Details

Author
IvanMurzak
Repository
IvanMurzak/Unity-MCP
Created
1 years ago
Last Updated
today
Language
C#
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category