Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    bix-claude-skills: GitHub PR Review Resolver

    1

    Triage GitHub PR comments, implement requested fixes, and sync replies directly from your terminal.

    Free

    Security scanned
    bix-claude-skills: GitHub PR Review Resolver

    bix-claude-skills: GitHub PR Review Resolver

    Example session with this skill installed

    Resolve the review comments on PR #42. Only look at unresolved threads.

    or

    /github-pr-resolve 128
    • Read your context and instructions
    • Compiled the bix-claude-

    Summary: PR #128 ("Add retry to invoice export") has 3 threads awaiting your reply and 1 review summary. The skill read the current code for each, found one project rule that applies (CLAUDE.md: no magic numbers), and asked you to triage. You chose Fix for thread 1, Reply only for thread 2 and Fix for thread 3. Changes are in your working tree and are not committed.

    Review summary

    
### Review by @mira-dev: CHANGES_REQUESTED
> A few small things in the export retry. Details inline.

    Threads

    
### Thread 1: src/export/retry.ts:42 (by @mira-dev) - [Agree-Fix]
> The delay of 500 should be a named constant.

Code context:
   const attempt = 0;
   while (attempt < 3) {
     await sleep(500);

Assessment: Reviewer is right. The value is repeated in two places and CLAUDE.md asks for named constants.

### Thread 2: src/export/retry.ts:77 (by @mira-dev) - [Disagree]
> Why not retry on every error?
  ↳ @tomas-r: Only network errors are safe to retry.

Code context:
   if (!isNetworkError(err)) throw err;

Assessment: Retrying a validation error would send the same bad invoice again. Current code is correct.

### Thread 3: src/export/csv.ts:19 (by @mira-dev) - [Agree-Fix]
> This header list is out of order compared to the docs.

Code context:
   const headers = ["id", "total", "date"];

Assessment: The docs list date before total. Fix.

    Final summary

    
### Fixed
- ✓ Thread 1 (src/export/retry.ts:42) - moved 500 to RETRY_DELAY_MS
- ✓ Thread 3 (src/export/csv.ts:19) - reordered headers to id, date, total

### Reply only
- Thread 2 (src/export/retry.ts:77) - [Disagree] Only network errors are retried, because other errors would fail the same way again.

### Skipped
- None

    Next steps

    • Review the diff, then ask the skill to commit.
    • Confirm the push when asked.
    • Approve the drafted replies, for example: "Fixed in a1b2c3d. The retry delay is now a named constant."
    • Answer "Mark these 2 threads as resolved?" for threads 1 and 3. Thread 2 stays open for the reviewer.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing PR feedback manually is slow and error-prone. This skill automates the evaluation, implementation, and resolution of GitHub pull request review comments. It stops you from context-switching between your terminal and browser by pulling review threads directly into your environment.

    What it does

    • Automated Triage pulls all active review threads and categorizes them as Agree-Fix, Clarify, Disagree, or Outdated.
    • Context-Aware Evaluation reads the current file state at specific lines to verify if reviewer feedback is still applicable before you act.
    • Rule Enforcement applies local project rules and .claude/rules to ensure suggested fixes align with your codebase conventions.
    • Batch Implementation creates focused tasks to apply agreed-upon changes across multiple files and threads.
    • Thread Management posts replies to GitHub using the correct API endpoints and offers to resolve threads only after confirmation.

    How it works

    1. Gather provides the PR number to fetch all active comments, code hunks, and repository-specific coding rules.
    2. Evaluate and display: read the code at each location, categorise, show summaries then threads by file.
    3. Triage: you pick an action per thread, up to 4 threads per question.
    4. Explore: investigate chosen threads and propose an approach for your approval.
    5. Implement: apply approved fixes one at a time with task tracking.
    6. Summary: list what was fixed, replied to and skipped. Nothing is committed yet.
    7. Commit, push, reply and resolve: each step waits for your confirmation.

    Frameworks & tools

    Uses the GitHub CLI (gh) and GraphQL API for repository interaction. Compatible with any stack as it operates on raw file content and PR metadata.

    Why this beats prompting it yourself

    Manual prompting often misses the full context of a review thread or ignores repository-specific linting and architectural rules. This skill systematically reads the exact code lines referenced, triages multiple threads in batches, and ensures every reply is concise and professional without AI branding.

    Use cases

    • Closing out large PRs with dozens of minor style and logic suggestions.
    • Defending architectural decisions by citing project rules in Disagree replies.
    • Responding to outdated comments after a rebase or significant refactor.

    Known limitations

    Requires the GitHub CLI to be authenticated. Performance may degrade with PRs exceeding 30 active threads, requiring file-by-file processing.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Free to download with an account

    Listed6 days ago

    What's inside

    Frequently Asked Questions