How do I install the Github Pr Workflow skill?

Run npx skillmds@latest add majiayu000/github-pr-workflow 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 Pr Workflow safe to use?

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

Which AI agents work with Github Pr Workflow?

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 Pr Workflow free to use?

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

Who published Github Pr Workflow?

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

Github Pr Workflow by majiayu000 — Agent Skill

Name: Github Pr Workflow
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

GitHub PR Workflow

Key Concepts

Comment Types

GitHub PRs have two different types of comments:

PR-level comments - General discussion on the PR (shown via gh pr view --comments)
Inline code review comments - Comments attached to specific lines of code (requires API)

Important: gh pr view --comments does NOT show inline code review comments!

Scripts

Script	Purpose
`gh-pr-review-comments <PR>`	Get inline code review comments (the ones `gh` misses!)
`gh-pr-summary <PR>`	PR title, description, state, branches
`gh-pr-reviews <PR>`	Review decisions (approved/changes requested)
`gh-pr-checks <PR>`	CI check status

All scripts auto-detect the repo from git remote, or accept [REPO] as second arg.

Common Commands

# Basic PR info
gh pr view <PR>                    # Overview
gh pr view <PR> --comments         # PR-level comments only (NOT inline!)
gh pr diff <PR>                    # View the diff

# Review comments (inline) - USE THE SCRIPT
gh-pr-review-comments <PR>         # ✅ Gets inline code review comments

# Or manually via API
gh api repos/OWNER/REPO/pulls/PR/comments | jq '.[] | {path, line, body}'

# Reviews (approve/request changes)
gh pr review <PR> --approve
gh pr review <PR> --request-changes --body "Please fix X"
gh pr review <PR> --comment --body "Looks good overall"

# Checks
gh pr checks <PR>                  # CI status
gh run view <RUN_ID> --log-failed  # Failed job logs

API Endpoints Reference

When gh commands don't expose what you need, use the API:

# Inline review comments
gh api repos/OWNER/REPO/pulls/PR/comments

# PR-level comments (issue comments)
gh api repos/OWNER/REPO/issues/PR/comments

# Review submissions
gh api repos/OWNER/REPO/pulls/PR/reviews

# Commits in PR
gh api repos/OWNER/REPO/pulls/PR/commits

# Files changed
gh api repos/OWNER/REPO/pulls/PR/files

Workflow: Addressing Review Comments

Get the comments: gh-pr-review-comments <PR>
Make fixes in your local branch
Push (if using JJ: jj git push)
Reply to comments on GitHub or via API
Re-request review if needed: gh pr edit <PR> --add-reviewer <USER>

---name: github-pr-workflowdescription: Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.--- # GitHub PR Workflow ## Key Concepts ### Comment Types GitHub PRs have **two different types of comments**: 1. **PR-level comments** - General discussion on the PR (shown via `gh pr view --comments`) 2. **Inline code review comments** - Comments attached to specific lines of code (requires API) **Important**: `gh pr view --comments` does NOT show inline code review comments! ## Scripts | Script | Purpose | |--------|---------| | `gh-pr-review-comments <PR>` | Get inline code review comments (the ones `gh` misses!) | | `gh-pr-summary <PR>` | PR title, description, state, branches | | `gh-pr-reviews <PR>` | Review decisions (approved/changes requested) | | `gh-pr-checks <PR>` | CI check status | All scripts auto-detect the repo from git remote, or accept `[REPO]` as second arg. ## Common Commands ```bash # Basic PR info gh pr view <PR> # Overview gh pr view <PR> --comments # PR-level comments only (NOT inline!) gh pr diff <PR> # View the diff # Review comments (inline) - USE THE SCRIPT gh-pr-review-comments <PR> # ✅ Gets inline code review comments # Or manually via API gh api repos/OWNER/REPO/pulls/PR/comments | jq '.[] | {path, line, body}' # Reviews (approve/request changes) gh pr review <PR> --approve gh pr review <PR> --request-changes --body "Please fix X" gh pr review <PR> --comment --body "Looks good overall" # Checks gh pr checks <PR> # CI status gh run view <RUN_ID> --log-failed # Failed job logs ``` ## API Endpoints Reference When `gh` commands don't expose what you need, use the API: ```bash # Inline review comments gh api repos/OWNER/REPO/pulls/PR/comments # PR-level comments (issue comments) gh api repos/OWNER/REPO/issues/PR/comments # Review submissions gh api repos/OWNER/REPO/pulls/PR/reviews # Commits in PR gh api repos/OWNER/REPO/pulls/PR/commits # Files changed gh api repos/OWNER/REPO/pulls/PR/files ``` ## Workflow: Addressing Review Comments 1. **Get the comments**: `gh-pr-review-comments <PR>` 2. **Make fixes** in your local branch 3. **Push** (if using JJ: `jj git push`) 4. **Reply to comments** on GitHub or via API 5. **Re-request review** if needed: `gh pr edit <PR> --add-reviewer <USER>`

Frequently asked questions

Github Pr Workflow