cmd-workflow-pr-fix

Categorize PR reviewer comments, implement fixes, and reply inline via GitHub CLI.

2|Updated Jan 3, 2026

Search Tags:#automation #git #github #review #pr #code-review #pull-request

Ready to run

npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-pr-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cmd-workflow-pr-fix
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-workflow-pr-fix
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-pr-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve PR reviewer comments by categorizing feedback, implementing fixes in the codebase, replying inline to reviewers, and validating changes before merging.

Core Features & Use Cases

Categorizes reviewer comments into blocking, questions, suggestions, and nitpicks.
Applies fixes only to files changed in the PR and creates atomic commits.
Replies inline to review threads with concise explanations and references to commits.
Verifies changes via tests, linting, and CI before push.

Quick Start

Identify an open PR with reviewer comments and start applying fixes following the workflow.

Frequently Asked Questions about cmd-workflow-pr-fix

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

FAQPage Schema

How do I automate resolving GitHub PR review comments?▼

Automate PR review comment resolution by categorizing feedback into blocking issues, questions, suggestions, and nitpicks, then implementing code fixes and replying inline to reviewers. It uses GitHub CLI commands to fetch PR details and apply changes scoped only to the files modified in the PR.

What is the best way to reply to code review comments inline on GitHub?▼

Replying inline to code review threads is handled by posting concise explanations directly to the specific reviewer comments. The workflow references the atomic commits where fixes were applied, ensuring clear traceability between the requested change and the implementation.

How do I categorize pull request feedback before applying code changes?▼

Categorize pull request feedback by parsing reviewer comments into distinct groups such as blocking issues, questions, suggestions, and nitpicks. This classification determines the priority of fixes and ensures only relevant code changes are implemented within the PR scope.

Does this PR fix workflow run tests and linting before pushing commits?▼

Yes, the PR fix workflow runs a verification process that includes tests, linting, and CI checks before pushing. It creates atomic commits for the fixes and ensures all changes are validated and confined to the PR scope prior to a push or merge.

Can I use GitHub CLI to manage and fix pull request review suggestions?▼

Yes, you can use GitHub CLI commands like 'gh pr view', 'gh pr diff', and 'gh api' to manage and fix pull request review suggestions. The workflow retrieves PR details and review feedback directly via the CLI to implement and verify the required code changes.

When should I not automate applying fixes from code review comments?▼

You should not automate applying fixes when the reviewer feedback requires architectural changes outside the current PR scope or open-ended design discussions. The workflow is designed for scoped code changes, linting verification, and structured atomic commits, not for resolving broad conceptual debates.