code-review
/code-review
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.
- Author
- yamcodes ↗
- Repository
- arkenv ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.
Original author description
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.
How it works
- Workflow Selection
- Mode A: Address / Fix Review Comments
- Mode B: Perform Code Review
SKILL.md preview
---
name: code-review
description: Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.
metadata:
internal: true
---
# Code Review
A dual-purpose skill to either (1) systematically retrieve and address pull request review comments on GitHub, or (2) perform a code review on changes in the workspace.
## Workflow Selection
At the start of execution, identify the user's intent:
- **Mode A: Address / Fix Review Comments**: Follow this mode if the user wants to address, fix, or resolve comments/feedback from a prior or active review (e.g., "fix PR comments", "address review notes", "resolve feedback", "address /code-review").
- **Mode B: Perform Code Review**: Follow this mode if the user wants a review of their changes or the current workspace (e.g., "review my code", "check these changes", "do a code review", "/code-review").
---
## Mode A: Address / Fix Review Comments
Systematically retrieve and fix comments from a PR review.
### 1. Locate current PR and comments
- Run `git status` to find the current branch.
- Run `gh pr status` to find the active pull request number and repository information.
- **Fetch Comments (Avoid Missing Inline Comments)**: Standard commands like `gh pr view <PR_NUMBER> --comments` only return high-level conversation summaries and **completely omit inline code review comments** made in the diff. To reliably retrieve the complete list of inline review comments, query the GitHub API directly:
```bash
gh api repos/:owner/:repo/pulls/<PR_NUMBER>/comments --jq '.[] | {id, path, line, body}'
```
### 2. Parse and analyze comments
- Extract the list of review comments. Focus on unresolved or actionable requests.
- For each comment, identify the affected file path, line numbers, and expected outcome.
- **Check for Stale/Addressed Comments**: Before making any code modifications, verify if the comment is already addressed or stale (e.g. if the target code has already been changed or deleted in a recent commit). Mark such comments as "Stale/Already Addressed" and skip them.
- **Handle Ambiguity / Ask for Clarification**: If a comment is ambiguous, lacks context, or if you are unsure of the best implementation path, STOP and ask the user for clarification. Do not make risky assumptions.
### 3. Implement the fixes
- View the surrounding code using the `view_file` tool to understand context.
- Update the code using `replace_file_content` or `multi_replace_file_content`. Keep changes minimal and adhere strictly to the codebase's existing code style, imports, and naming patterns.
### 4. Verify changes
- Compile/build the package (e.g., `pnpm build`, `npm run build`, or `tsc --noEmit`).
- Run the test suite (e.g., `pnpm test`, `npm test`, or `vitest`) to ensure all tests pass.
- Run size limit checks if applicable.
### 5. Report results & comment back
- Present a clear markdown table summarizing:
- Review comment / concern.
- File and lines changed.
- Action taken (e.g., "Fixed", "Already Addressed", "Skipped").
- Verification status.
- **Comment and Resolve on PR**: Always reply to and resolve addressed threads on GitHub:
- **Reply**: Post a reply to the thread using the REST API (with the database ID of the last comment):
```bash
gh api -X POST /repos/:owner/:repo/pulls/<PR_NUMBER>/comments/<comment_id>/replies -f body="Addressed in latest commit."
```
- **Resolve Thread**: Mark the thread as resolved using the GraphQL API (using the GraphQL thread ID `PRRT_...`):
```bash
gh api graphql -F threadId="<thread_id>" -f query='
mutation($threadId: ID!) {
resolveReviewThread(input: { threadId: $threadId }) {
thread { id isResolved }
}
}
'
```
- **General Comment**: To add a general comment to the PR:
```bash
gh pr comment <PR_NUMBER> --body "Addressed review comments: ..."
```
---
## Mode B: Perform Code Review
Perform a high-quality, professional code review of the workspace changes.
### 1. Retrieve changes
- Run `git status` to check modified files.
- Run `git diff` (or compare branches) to retrieve the full diff of the changes under review.
### 2. Analyze the changes
Review the diff/code for:
- **Correctness & Bugs**: Off-by-one errors, edge cases, incorrect conditional logic.
- **TypeScript & Types**: Stale or weak types, unsafe casts, unused imports or variables.
- **Dead Code**: Functions, imports, or files that are defined but never used.
- **Stale JSDoc & Docs**: Stale doc comments that refer to renamed functions or old signatures.
- **Architectural Patterns**: Consistency with the repository's architecture (e.g. modular structure, proper abstraction boundaries).
### 3. Report review findings
Output the code review structured by file:
- For each file, list specific findings with line numbers and recommendations.
- Categorize findings into:
- ⚠️ **Critical / Issues**: Bugs, type/compilation errors, or logic issues.
- ℹ️ **Refactors / Cleanup**: Dead code, unused imports, stale JSDoc.
- 💡 **Suggestions / Nits**: Minor styling, readability improvements, or alternative approaches.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · yamcodes/arkenv | 100 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 47fc4196c0e7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90address-review
Fetch GitHub PR review comments, triage them into must-fix/discuss/optional/skipped, and guide fixing or replying to selected feedback. Use when addressing PR review comments or review threads. - 95factory-github
Work with GitHub through the gh CLI — reading PR reviews and line comments, checking CI status, reading issues, and replying to review feedback. Use whenever a GitHub URL, PR number or issue is mentioned, or when asked to address review comments. Covers the reply-with-what-changed convention. - 100github-pr-comments
Resolve inline code review comments on a GitHub PR. Use when asked to "resolve review comments", "address PR feedback", "fix PR comments", or "work through review comments". Fetches every inline comment with its surrounding code context, then applies each change systematically. - 100review-pr-comments
Use when the user wants to address, process, or work through GitHub PR review comments. Trigger on phrases like "address PR comments", "work through review comments", "process PR feedback", "apply reviewer suggestions", or "/review-pr-comments <number>". - 90address-pr-comments
Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues. - 90address-code-review
Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the repo, or directly in conversation — and wants to work through them methodically. Also trigger when the…