An automation workflow for handling review comments on GitHub pull requests, which are proposed code changes submitted for team review. It reads the comments, checks out the relevant branch, and applies fixes for the requested feedback.

Fetching pull-request details and review comments, switching to the correct branch, applying fixes requested by reviewers, and updating the code to address review suggestions.

It removes the manual work of finding every review comment, opening the correct code version, and making the corresponding changes. It is intended for requests to address or resolve pull-request feedback.

fix-issues — Skill for Claude Code by stilero/claude-plugins

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add stilero/claude-plugins --skill fix-issues

Clone the repo

git clone --depth 1 https://github.com/stilero/claude-plugins

Made for: Claude Code.

Or install pr-comment-fixer, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stilero/claude-plugins/fix-issues/github.svg)](https://agentmods.dev/skills/stilero/claude-plugins/fix-issues)

Your own site

<a href="https://agentmods.dev/skills/stilero/claude-plugins/fix-issues"><img src="https://agentmods.dev/badge/skills/stilero/claude-plugins/fix-issues/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stilero/claude-plugins/fix-issues"><img src="https://agentmods.dev/badge/skills/stilero/claude-plugins/fix-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,018 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.01018
Opus 5.5	$0.00024	$0.00407
Sonnet 5.5	$0.00012	$0.00204
Haiku 4.5	$0.00006	$0.00102

Measured 1mo ago against content hash 66638526be2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fix-issues scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pr-comment-fixer/skills/fix-issues/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Comment Fixer

Automatically processes GitHub pull request review comments and applies code fixes to address reviewer feedback.

Workflow

Follow this workflow when the user requests PR comment fixes:

1. Extract PR Information

Parse the PR number from the user's request. Accept formats like:

"PR #1234"
"pull request 1234"
"#1234"
Just the number "1234"

2. Fetch PR Details

Use GitHub CLI to get PR information:

gh pr view <PR_NUMBER> --json number,title,headRefName,repository

Extract:

headRefName: The PR branch name
repository: Owner and repo name

3. Ensure Repository Access

Check if running locally or remotely:

git rev-parse --git-dir 2>/dev/null

If this fails (not in a git repository):

Clone the repository: gh repo clone <OWNER>/<REPO>
Change to repository directory

If successful (already in repository):

Verify it's the correct repository
Continue with existing local clone

4. Checkout PR Branch

Switch to the PR branch:

git fetch origin
git checkout <BRANCH_NAME>
git pull origin <BRANCH_NAME>

5. Fetch All PR Comments

Retrieve review comments using GitHub CLI:

gh pr view <PR_NUMBER> --json reviews,comments --jq '.reviews[].comments[], .comments[]'

Parse the JSON output to extract:

Comment body/text
File path (if applicable)
Line number or diff position
Author
Whether it's resolved or pending

6. Evaluate Comment Relevance

For each comment, determine if it's actionable:

Actionable comments (should be fixed):

Requests for code changes (naming, formatting, refactoring)
Bug reports or logic errors
Suggestions for improvements
Security or performance concerns
Missing error handling
Code quality issues

Non-actionable comments (skip):

General discussion or questions already answered
Comments marked as resolved
Informational comments with no change request
Compliments or approvals

When in doubt, err on the side of treating comments as actionable.

Read the full file on GitHub · 158 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 158 lines · 60 tokens per session scan A 66638526be2b

Subscribe to this mod's changes

fix-issues is a skill published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,018 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Git and workflow

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens