code-review-resolver

Resolve GitHub PR review comments by analyzing commit history and agent context.

1|Updated Jul 11, 2019

Search Tags:#automation #github #graphql #bot #code-review #pull-request #rest-api

Ready to run

npx skills add https://github.com/crsiebler/dotfiles --skill code-review-resolver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-resolver
Source: https://github.com/crsiebler/dotfiles/tree/main/ai/opencode/skills/code-review-resolver
Command: npx skills add https://github.com/crsiebler/dotfiles --skill code-review-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically identifies and resolves GitHub PR review comments by analyzing commit history and agent context.

Core Features & Use Cases

Fetches PR review comments and maps them to threads
Analyzes commit history and agent context to determine resolved status
Automatically resolves identified threads via GraphQL mutation
Provides feedback and dry-run previews
Use after pushing fixes to clean up review threads and ensure clean merges

Quick Start

Provide a PR number and I will analyze commits and context to resolve eligible review threads.

Frequently Asked Questions about code-review-resolver

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

FAQPage Schema

How do I automatically resolve GitHub PR review comments after pushing fixes?▼

You can automatically resolve GitHub PR review comments by analyzing commit history and agent context to identify resolved threads. This process maps review comments to threads and applies GraphQL mutations to close eligible conversations automatically.

Can I preview which pull request threads will be auto-resolved before making changes?▼

Yes, you can run a dry-run preview to see which pull request threads the analysis identifies as eligible for resolution. This allows you to verify the commit history and agent context mapping before applying any automatic thread changes.

Does resolving GitHub PR review threads require the GraphQL API or REST API?▼

Resolving GitHub PR review threads requires the GraphQL API to apply mutations that close the conversations. The REST API is also utilized alongside GraphQL for fetching PR review comments and mapping them to their respective threads.

What is the best way to reduce manual code review overhead on pull requests with multiple threads?▼

The best way to reduce manual code review overhead is to use an automated bot that analyzes commit history and agent context. It determines which feedback has been addressed and automatically resolves the corresponding review threads.

What methods are available for determining resolved status when auto-resolving PR review comments?▼

The available methods for determining resolved status are commit-history analysis and agent-context analysis. Both methods evaluate the pull request state to identify which review threads have been successfully addressed.

Can I configure the resolution scope for auto-resolving pull request review comments?▼

Yes, you can configure the resolution scope when auto-resolving pull request review comments. This allows you to control which threads the bot targets, alongside options for dry-run previews and optional auto-resolve workflows.