code-review

Fetch and address GitHub pull request review comments or review workspace code changes.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/yamcodes/the-hat --skill code-review-yamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yamcodes/the-hat/tree/main/skills/code-review
Command: npx skills add https://github.com/yamcodes/the-hat --skill code-review-yamcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing code and responding to pull request feedback involves tedious manual steps: hunting down inline comments, checking whether they are still relevant, making fixes, verifying builds, and replying on GitHub. This Skill automates that entire loop so no review comment gets missed or left unresolved. ## Core Features & Use Cases - Address PR Review Comments: Retrieves all inline review comments via the GitHub API (including ones gh pr view omits), checks for stale or already-addressed items, implements minimal fixes, and replies to and resolves threads on GitHub. - Perform Code Reviews: Analyzes workspace diffs for correctness bugs, weak TypeScript types, dead code, stale JSDoc, and architectural inconsistencies, then reports findings categorized as Critical, Refactors, or Suggestions. - Use Case: A teammate left 12 inline comments on your pull request. Ask the assistant to address the review, and it will fetch every comment, fix the actionable ones, run the build and tests, post replies, and resolve each thread. ## Quick Start Ask the assistant to address the review comments on my current pull request and resolve the threads on GitHub.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I address all review comments on a GitHub pull request?▼

Fetch inline comments with `gh api repos/:owner/:repo/pulls/<PR>/comments`, since `gh pr view --comments` omits diff-level comments. Then implement fixes per comment, verify with build and tests, and reply to and resolve each thread via the API.

How to perform a code review on uncommitted workspace changes?▼

Run `git status` and `git diff` to retrieve the changes, then analyze them for correctness bugs, weak types, dead code, stale JSDoc, and architectural inconsistencies. Report findings per file categorized as Critical, Refactors, or Suggestions.

Why are inline PR review comments missing from gh pr view?▼

The `gh pr view --comments` command only returns high-level conversation summaries and omits inline diff comments. Query the GitHub REST API endpoint `pulls/<PR_NUMBER>/comments` directly to retrieve the complete list of inline review comments.

How do I resolve a review thread on GitHub from the command line?▼

Use the GitHub GraphQL API with the `resolveReviewThread` mutation, passing the thread's GraphQL ID (starting with `PRRT_`). To reply first, POST to the REST endpoint `pulls/<PR>/comments/<comment_id>/replies` with the comment's database ID.

What should I do when a review comment is ambiguous or already fixed?▼

Check whether the target code has already changed or been deleted in recent commits and mark such comments as stale or already addressed. If a comment lacks context or the implementation path is unclear, stop and ask the requester for clarification rather than guessing.