fix-pr-reviews
Fix PR Reviews
Automatically fetch and fix valid code review findings from PR comments and/or local review markdown files.
Sources
This skill pulls findings from two sources (either or both):
-
PR comments (automatic) — Fetched from the open PR for the current branch via
gh. Includes:- GitHub PR review comments (inline code comments)
- PR review bodies (top-level review summaries)
- General PR comments that contain code review content
- Filters for comments that look like code reviews (mentions files, lines, bugs, suggestions, code snippets, etc.) from any reviewer — AI agents (Claude Code, Codex, Copilot, etc.) and humans alike.
-
Local review files (if provided) — Markdown files the user passes explicitly (e.g.,
review1.md,review2.md). Accept any number of files in any format (structured or free-form).
Workflow
- Determine the PR — Run
gh pr list --head <current-branch> --json number,url --jq '.[0]'to find the open PR for the current branch. If no PR exists and no local files are provided, inform the user and stop.
More from ilamanov/skills
spec-builder
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
23pr
Commit changes and create or update a pull request following project standards. Use when the user wants to commit work, create a PR, update an existing PR, or use the /pr command.
14reimplement-branch
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when the user wants to clean up messy commits, create a tutorial-style commit history, or prepare a branch for review with logical, self-contained commits. Triggers on requests like "clean up my commits", "reimplement this branch", "create a clean history", or "make my commits reviewable".
12deslop
Remove AI-generated code slop from the current branch. Use when the user says "deslop" or asks to clean up AI slop, remove AI code patterns, or clean the branch before committing.
9compile-conversation-into-doc
Turn long, messy AI chat conversations into clear, durable, and easily scannable reference documents that humans can reliably return to weeks or months later.
9review-bug-fixer
Fix valid code review findings from one or more review markdown files. Use when the user has review files (e.g., review1.md, review2.md) containing code review findings, issues, or suggestions and wants to fix the valid ones in the current branch. Triggers on requests like "fix review findings", "fix issues from review", "apply code review fixes", or any mention of fixing bugs/issues from review markdown files.
8