bms:resolve-pr-comments

Resolve open GitHub PR comments by applying and pushing fixes.

68|14|Updated Dec 21, 2017
One-click install
npx skills add https://github.com/benmatselby/dotfiles --skill bms-resolve-pr-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bms:resolve-pr-comments
Source: https://github.com/benmatselby/dotfiles/tree/main/agents/skills/resolve-pr-comments
Command: npx skills add https://github.com/benmatselby/dotfiles --skill bms-resolve-pr-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review open review comments on a GitHub PR, align with the user on a fix, apply the changes to the branch, commit, push to GitHub, and mark the thread as resolved.

Core Features & Use Cases

  • Fetch open, unresolved review comments from a PR.
  • Present each comment to the user with context, suggested fixes, and recommended actions.
  • Check out the PR branch, apply approved changes, and prepare commits for push.
  • Create a patch, commit, and push to the PR repository, then mark the thread as resolved via GraphQL.
  • Report back to the user and proceed to the next unresolved comment.

Quick Start

Provide a GitHub PR URL to begin reviewing unresolved comments and guiding the user through applying and pushing fixes.

Frequently Asked Questions about bms:resolve-pr-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate resolving GitHub pull request comments?

Automate GitHub pull request comment resolution by fetching unresolved comments, guiding step-by-step edits, committing changes, pushing to the PR branch, and marking threads as resolved. Provide a GitHub PR URL to begin the automated review and fix workflow.

What is the step-by-step process to apply code review fixes to a pull request?

Applying code review fixes involves checking out the PR branch, applying approved changes one at a time, creating a patch, committing, and pushing to the repository. The process repeats for each unresolved comment until all threads are resolved.

Do I need gh CLI authentication to resolve PR review threads?

Yes, gh CLI authentication is required to resolve PR review threads. The process relies on gh CLI and GraphQL to verify thread resolution and handle PR checkout and push flows safely before making any commits to the repository.

Can I review and fix unresolved GitHub PR comments one at a time?

Yes, you can review and fix unresolved GitHub PR comments one at a time. The workflow presents each unresolved comment with context and suggested fixes, waits for user agreement, applies the change, and then proceeds to the next unresolved comment.

How are resolved PR threads verified using GraphQL?

Resolved PR threads are verified using GraphQL queries after pushing commits to GitHub. The workflow marks each thread as resolved via GraphQL API calls and reports the resolution status back to the user before moving to the next comment.

What's the best way to handle multiple open code review comments on a GitHub PR?

The best way to handle multiple open code review comments is presenting each comment individually with context and recommended actions, securing user agreement on fixes, and automating the commit, push, and thread resolution cycle for each unresolved item sequentially.