How do I install the Github Code Review skill?

Run npx skillmds@latest add rivie13-phoenix-agentic-engine-interface/github-code-review 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 Github Code Review safe to use?

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

Which AI agents work with Github Code Review?

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 Github Code Review free to use?

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

Who published Github Code Review?

rivie13 (@rivie13-phoenix-agentic-engine-interface) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Code Review by rivie13-phoenix-agentic-engine-interface

Name: Github Code Review
Rating: 4.2 (5 reviews)
Author: rivie13

Github Code Review

Fetch and address GitHub pull request code review comments, including Copilot code reviews. Use when user asks to get review feedback, address review comments, fix review issues, request a code review, check PR reviews, or respond to reviewer feedback.

rivie13 Updated Sep 10, 2026

File contents

GitHub Code Review — Phoenix Agentic Engine Interface

Repo Context

Owner: rivie13
Repo: Phoenix-Agentic-Engine-Interface
Type: Public (TS SDK + Contracts)

Workflow: Fetch & Address Review Comments

Step 1: Identify the PR

If the user doesn't specify a PR number, list open PRs:

mcp_github_github_list_pull_requests(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", state="open")

Step 2: Get review comments

mcp_github_github_pull_request_read(method="get_review_comments", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)

Get review status:

mcp_github_github_pull_request_read(method="get_reviews", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)

Step 3: Get changed files for context

mcp_github_github_pull_request_read(method="get_files", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)

Step 4: Address each unresolved comment

For each unresolved review thread:

Read the file and surrounding context using read_file
Understand the reviewer's concern
Make the fix using file edit tools
Report what was changed and why

Step 5: Request a new review (optional)

Only request a new Copilot review if either:

no prior Copilot review exists on the PR, or
new commits were pushed after the latest Copilot review.

If Copilot comments already exist for the latest commit set, address those comments first before requesting another review.

mcp_github_github_request_copilot_review(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)

Review priorities for this repo

When addressing reviews, keep these Interface SDK review priorities in mind:

This is a protocol layer — no UI, no orchestration, no business logic
Schema changes in contracts/v1/ are potentially breaking — require justification
No orchestration logic, prompt content, or agent coordination (those belong in Backend)
Use strict TypeScript (strict: true) — flag any any usage
Use Zod schemas for runtime validation
Keep dependencies minimal — every new dep is a supply chain risk
Ensure contract fixture compatibility tests still pass
Run npm test and npm run typecheck after fixes

---name: github-code-reviewdescription: Fetch and address GitHub pull request code review comments, including Copilot code reviews. Use when user asks to get review feedback, address review comments, fix review issues, request a code review, check PR reviews, or respond to reviewer feedback.---# GitHub Code Review — Phoenix Agentic Engine Interface## Repo Context- **Owner**: `rivie13`- **Repo**: `Phoenix-Agentic-Engine-Interface`- **Type**: Public (TS SDK + Contracts)## Workflow: Fetch & Address Review Comments### Step 1: Identify the PRIf the user doesn't specify a PR number, list open PRs:```mcp_github_github_list_pull_requests(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", state="open")```### Step 2: Get review comments```mcp_github_github_pull_request_read(method="get_review_comments", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)```Get review status:```mcp_github_github_pull_request_read(method="get_reviews", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)```### Step 3: Get changed files for context```mcp_github_github_pull_request_read(method="get_files", owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)```### Step 4: Address each unresolved commentFor each unresolved review thread:1. Read the file and surrounding context using `read_file`2. Understand the reviewer's concern3. Make the fix using file edit tools4. Report what was changed and why### Step 5: Request a new review (optional)Only request a new Copilot review if either:- no prior Copilot review exists on the PR, or- new commits were pushed after the latest Copilot review.If Copilot comments already exist for the latest commit set, address those comments first before requesting another review.```mcp_github_github_request_copilot_review(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", pullNumber=<PR_NUMBER>)```## Review priorities for this repoWhen addressing reviews, keep these Interface SDK review priorities in mind:- This is a **protocol layer** — no UI, no orchestration, no business logic- Schema changes in `contracts/v1/` are potentially breaking — require justification- No orchestration logic, prompt content, or agent coordination (those belong in Backend)- Use strict TypeScript (`strict: true`) — flag any `any` usage- Use Zod schemas for runtime validation- Keep dependencies minimal — every new dep is a supply chain risk- Ensure contract fixture compatibility tests still pass- Run `npm test` and `npm run typecheck` after fixes

Frequently asked questions