resolve-review

Fetch GitHub PR review comments, apply fixes, run pre-commit linting, and stage changes.

8.0k|721|Updated Jun 15, 2023
One-click install
npx skills add https://github.com/InternLM/lmdeploy --skill resolve-review-internlm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-review
Source: https://github.com/InternLM/lmdeploy/tree/main/.claude/skills/resolve-review
Command: npx skills add https://github.com/InternLM/lmdeploy --skill resolve-review-internlm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and resolve PR review comments to produce concrete code changes ready for review and merging.

Core Features & Use Cases

  • Fetch PR review comments from a GitHub Pull Request and map them to actionable fixes.
  • Apply fixes across the codebase, run pre-commit linting, and prepare changes for commit and push.
  • Use-case: when maintainers annotate PRs with issues, this skill automates turning those comments into committed patches.

Quick Start

Provide the PR number to fetch comments, apply fixes, lint the changes, and push.

Frequently Asked Questions about resolve-review

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

FAQPage Schema
How do I automate fixing GitHub PR review comments with code changes?

To automate fixing GitHub PR review comments, this skill fetches the annotations, maps them to actionable code fixes, applies the patches to the corresponding files, and stages the changes. You simply provide the PR number to generate and push committed fixes.

How do I run pre-commit linting automatically after applying PR code fixes?

Running pre-commit linting after applying PR code fixes happens automatically within the PR workflow. The skill applies the fetched review fixes to the codebase and then executes the configured pre-commit linting setup to validate and prepare the changes for commit and push.

Do I need GitHub authentication to fetch and resolve pull request review comments?

Yes, you need GitHub authentication and repository access to fetch and resolve pull request review comments. A properly configured lint and pre-commit setup is also required to validate the applied code fixes and push the staged changes for the PR workflow.

What's the best way to turn maintainer PR annotations into committed git patches?

The best way to turn maintainer PR annotations into committed git patches is using an automated skill that fetches review comments, generates concrete code fixes, applies them across files, and runs pre-commit linting. This prepares the changes directly for commit and push.

Why does applying PR code fixes fail without a properly configured pre-commit setup?

Applying PR code fixes fails without a properly configured pre-commit setup because the skill requires linting validation to ensure code quality before staging. The pre-commit setup validates the applied changes, and without it, the automated PR workflow cannot safely push the fixes.