gh-modify-pr

# 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:
3. - `gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision`
4. Fetch inline review comments:
5. - `gh api repos/<owner>/<repo>/pulls/<number>/comments`
6. Extract actionable items from comment bodies.
7. Ensure local repo exists in workspace:
8. - If missing: `git clone [email protected]:<owner>/<repo>.git`
9. Checkout PR branch in local repo:
10. - `gh pr checkout <number>`
11. Open affected files and implement requested changes exactly.
12. Validate changed files quickly (lint/test only if needed or requested).
13. Commit:
14. - `git add <files>`
15. - `git commit -m "<clear message>"`
16. Report back with:
17. - What changed
18. - Commit hash
19. - Branch name
20. Push only if user asks/approves:
21. - `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`