How do I install the Gh Modify Pr skill?

Run npx skillmds@latest add modbender/gh-modify-pr 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 Gh Modify Pr 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 Gh Modify Pr?

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

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

Who published Gh Modify Pr?

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

Gh Modify Pr by modbender — Agent Skill

Name: Gh Modify Pr
Rating: 4.2 (5 reviews)
Author: modbender

Gh Modify Pr

Modify code based on GitHub PR review comments and create a local commit using gh + git. Use when the user asks to "follow PR comments", "fix review comments", "update this PR", or provides a PR URL and asks for edits/commit.

modbender Updated Sep 9, 2026 12 repo stars

File contents

gh-modify-pr

Use this workflow for PR-comment-driven changes.

Inputs

PR URL (preferred), e.g. https://github.com/owner/repo/pull/123
Optional scope from user (e.g. only one comment, all unresolved comments)

Workflow

Parse owner/repo and PR number from URL.
Inspect PR summary:
- gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision
Fetch inline review comments:
- gh api repos/<owner>/<repo>/pulls/<number>/comments
Extract actionable items from comment bodies.
Ensure local repo exists in workspace:
- If missing: git clone git@github.com:<owner>/<repo>.git
Checkout PR branch in local repo:
- gh pr checkout <number>
Open affected files and implement requested changes exactly.
Validate changed files quickly (lint/test only if needed or requested).
Commit:
- git add <files>
- git commit -m "<clear message>"
Report back with:

What changed
Commit hash
Branch name

Push only if user asks/approves:

git push

Rules

Prefer minimal diffs that address reviewer intent directly.
Do not silently alter unrelated code.
If a comment is ambiguous, ask one focused clarification question.
If no local repo exists, clone first instead of failing.
Include failed attempts in the final operation log when user asks for traceability.

Handy commands

# PR meta
gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision

# Inline review comments
gh api repos/<owner>/<repo>/pulls/<number>/comments

# Checkout PR branch (inside repo)
gh pr checkout <number>

# Status and commit
git status --short
git add <files>
git commit -m "chore: address PR review comments"

Output template

PR: <url>
Addressed comments: <n>
Changed files:
- <path>: <summary>
Commit: <hash>
Branch: <branch>
Pushed: yes/no

---name: gh-modify-prdescription: Modify code based on GitHub PR review comments and create a local commit using gh + git. Use when the user asks to "follow PR comments", "fix review comments", "update this PR", or provides a PR URL and asks for edits/commit.--- # gh-modify-pr Use this workflow for PR-comment-driven changes. ## Inputs - PR URL (preferred), e.g. `https://github.com/owner/repo/pull/123` - Optional scope from user (e.g. only one comment, all unresolved comments) ## Workflow 1. Parse owner/repo and PR number from URL. 2. Inspect PR summary: - `gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision` 3. Fetch inline review comments: - `gh api repos/<owner>/<repo>/pulls/<number>/comments` 4. Extract actionable items from comment bodies. 5. Ensure local repo exists in workspace: - If missing: `git clone git@github.com:<owner>/<repo>.git` 6. Checkout PR branch in local repo: - `gh pr checkout <number>` 7. Open affected files and implement requested changes exactly. 8. Validate changed files quickly (lint/test only if needed or requested). 9. Commit: - `git add <files>` - `git commit -m "<clear message>"` 10. Report back with: - What changed - Commit hash - Branch name 11. Push only if user asks/approves: - `git push` ## Rules - Prefer minimal diffs that address reviewer intent directly. - Do not silently alter unrelated code. - If a comment is ambiguous, ask one focused clarification question. - If no local repo exists, clone first instead of failing. - Include failed attempts in the final operation log when user asks for traceability. ## Handy commands ```bash # PR meta gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision # Inline review comments gh api repos/<owner>/<repo>/pulls/<number>/comments # Checkout PR branch (inside repo) gh pr checkout <number> # Status and commit git status --short git add <files> git commit -m "chore: address PR review comments" ``` ## Output template - PR: `<url>` - Addressed comments: `<n>` - Changed files: - `<path>`: `<summary>` - Commit: `<hash>` - Branch: `<branch>` - Pushed: `yes/no`

Frequently asked questions