How do I install the Pr Review Coordinator skill?

Run npx skillmds@latest add tomevault-io/pr-review-coordinator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Review Coordinator safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Review Coordinator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Review Coordinator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Review Coordinator?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Review Coordinator by tomevault-io

Name: Pr Review Coordinator
Author: tomevault-io

Pr Review Coordinator

Orchestrates PR review issue resolution by parsing review comments and dispatching to pr-issue-fixer subagents. Use when given a PR review summary, list of issues to fix, or when the user pastes review comments from CodeRabbit, Claude, Cursor, or similar tools. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

PR Review Coordinator

Parses PR review feedback and dispatches issues to pr-issue-fixer subagents for resolution.

Workflow

Step 1: Parse Issues

Extract issues from the review. Look for:

Source	Patterns to Find
CodeRabbit	"Actionable comments", severity badges, file paths with line numbers
Claude bot	Priority sections (Critical/High/Medium/Low), code suggestions
Cursor bot	Numbered suggestions with code snippets
Manual	Bulleted/numbered issues with descriptions

For each issue, extract:

- File: (required) path/to/file.ts
- Lines: (optional) 45-50 or 123
- Priority: Critical > High > Medium > Low
- Category: cache-management | error-handling | performance | code-style | testing | documentation | security | architecture
- Problem: What's wrong
- Suggestion: The fix (preserve code snippets!)

Step 2: Group and Prioritize

Sort by priority (Critical first)
Group by file (same-file issues run sequentially)
Flag conflicts (multiple issues on same lines)

Step 3: Dispatch to Fixers

Use the Task tool with subagent_type="pr-issue-fixer":

Use Task tool:
- subagent_type: "pr-issue-fixer"
- prompt: |
    Fix this PR review issue:
    - File: [path]
    - Lines: [numbers]
    - Priority: [level]
    - Category: [category]
    - Problem: [description]
    - Suggestion: [fix with code snippets]
    - Context: [relevant architecture info]
    
    After fixing, run verification and report status.

Parallelization:

PARALLEL: Issues in different files
SEQUENTIAL: Issues in the same file

Step 4: Compile Results

After all fixers complete:

## PR Review Resolution Summary

### Processed: X issues

| Status | File | Issue |
|--------|------|-------|
| ✅ | path/file.ts | Brief description |
| ⚠️ | path/other.ts | Partial - [what remains] |
| ❌ | path/broken.ts | [reason] |

### Verification
- Typecheck: ✅/❌
- Tests: N passed, M failed

### Follow-up
- [ ] Items needing human review

Step 5: Final Verification

Run after all issues addressed:

pnpm nx typecheck <project>
pnpm nx test <project> --watch=false

Example

Input:

CodeRabbit review:
1. [High] apps/ui/utils/cache.ts:45 - Cache unbounded, add LRU
2. [Medium] apps/ui/worker.ts:123 - Memory leak in cleanup

Actions:

Parse → 2 issues, 2 different files
Dispatch in parallel (different files)
Collect results
Run final verification
Report summary

Guidelines

Preserve code snippets from suggestions
Skip "nitpick" or "optional" issues unless requested
For vague issues, include surrounding review context
Flag conflicting suggestions for human decision

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: pr-review-coordinatordescription: Orchestrates PR review issue resolution by parsing review comments and dispatching to pr-issue-fixer subagents. Use when given a PR review summary, list of issues to fix, or when the user pastes review comments from CodeRabbit, Claude, Cursor, or similar tools. Use when this capability is needed.---# PR Review CoordinatorParses PR review feedback and dispatches issues to `pr-issue-fixer` subagents for resolution.## Workflow### Step 1: Parse IssuesExtract issues from the review. Look for:| Source | Patterns to Find ||--------|------------------|| CodeRabbit | "Actionable comments", severity badges, file paths with line numbers || Claude bot | Priority sections (Critical/High/Medium/Low), code suggestions || Cursor bot | Numbered suggestions with code snippets || Manual | Bulleted/numbered issues with descriptions |For each issue, extract:```- File: (required) path/to/file.ts- Lines: (optional) 45-50 or 123- Priority: Critical > High > Medium > Low- Category: cache-management | error-handling | performance | code-style | testing | documentation | security | architecture- Problem: What's wrong- Suggestion: The fix (preserve code snippets!)```### Step 2: Group and Prioritize1. Sort by priority (Critical first)2. Group by file (same-file issues run sequentially)3. Flag conflicts (multiple issues on same lines)### Step 3: Dispatch to FixersUse the Task tool with `subagent_type="pr-issue-fixer"`:```Use Task tool:- subagent_type: "pr-issue-fixer"- prompt: | Fix this PR review issue: - File: [path] - Lines: [numbers] - Priority: [level] - Category: [category] - Problem: [description] - Suggestion: [fix with code snippets] - Context: [relevant architecture info] After fixing, run verification and report status.```**Parallelization:**- PARALLEL: Issues in different files- SEQUENTIAL: Issues in the same file### Step 4: Compile ResultsAfter all fixers complete:```markdown## PR Review Resolution Summary### Processed: X issues| Status | File | Issue ||--------|------|-------|| ✅ | path/file.ts | Brief description || ⚠️ | path/other.ts | Partial - [what remains] || ❌ | path/broken.ts | [reason] |### Verification- Typecheck: ✅/❌- Tests: N passed, M failed### Follow-up- [ ] Items needing human review```### Step 5: Final VerificationRun after all issues addressed:```bashpnpm nx typecheck <project>pnpm nx test <project> --watch=false```## Example**Input:**```CodeRabbit review:1. [High] apps/ui/utils/cache.ts:45 - Cache unbounded, add LRU2. [Medium] apps/ui/worker.ts:123 - Memory leak in cleanup```**Actions:**1. Parse → 2 issues, 2 different files2. Dispatch in parallel (different files)3. Collect results4. Run final verification5. Report summary## Guidelines- Preserve code snippets from suggestions- Skip "nitpick" or "optional" issues unless requested- For vague issues, include surrounding review context- Flag conflicting suggestions for human decision---> Converted and distributed by [TomeVault](https://tomevault.io/claim/taucad) — claim your Tome and manage your conversions.

Frequently asked questions