skills.rest
nearai
nearaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-review

Analyze GitHub pull requests or local diffs for bugs, security issues, and missing tests.

12.6k|1.5k|Updated Feb 3, 2026
Search Tags:#diff analysis#architecture#code review#security#github#pull requests#test coverage
One-click install
npx skills add https://github.com/nearai/ironclaw --skill code-review-nearai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nearai/ironclaw/tree/main/skills/code-review
Command: npx skills add https://github.com/nearai/ironclaw --skill code-review-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github.

What problem does it solve?

It helps teams catch bugs, security issues, missing tests, and risky assumptions in code changes before they ship, including when changes arrive via a local diff or a GitHub pull request.

Core Features & Use Cases

  • GitHub PR paranoid review: Fetches PR metadata, unified diff, and per-file patch summaries, then produces findings with severity, category, and concrete fixes.
  • Local diff review: Runs the same deep-review lenses for unstaged/staged diffs or the previous commit and reports findings in-chat.
  • Line-level comment posting: For PRs, can post selected findings as RIGHT-side, line-anchored review comments using the PR head commit SHA.
  • Six-lens quality checklist: Evaluates correctness, edge cases, security, test coverage, documentation/assumptions, and architectural concerns.

Quick Start

Ask the AI to run the code-review skill on owner/repo#123 to produce a paranoid architect review and recommend which findings to comment on.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check a GitHub pull request for security vulnerabilities and bugs?▼

To check a GitHub pull request for security vulnerabilities, fetch PR metadata and unified diff content, then analyze changes for bugs, missing tests, and undocumented assumptions using a paranoid architect review.

Can I post line-level review comments on a GitHub PR diff automatically?▼

Yes, you can post line-level review comments by anchoring findings to the RIGHT side of the diff using the PR head commit SHA, providing actionable suggested fixes directly on the code.

Does this code review tool work with local unstaged or staged diffs?▼

Yes, the code review tool works with local unstaged or staged diffs and previous commits, applying the same deep-review lenses and reporting findings directly in-chat.

What specific categories does the code review checklist evaluate?▼

The code review checklist evaluates six categories: correctness, edge cases, security, test coverage, documentation or assumptions, and architectural concerns.

Do I need GitHub access to run a paranoid code review on my changes?▼

No, GitHub access is not required to run a paranoid code review; you can analyze local diffs or previous commits directly, though GitHub is needed for fetching PRs and posting comments.

How should code review findings be structured for actionable fixes?▼

Code review findings should be structured with file and line ranges, severity categorization, category labels, and concrete suggested fixes to ensure actionable remediation.

Related Skills

Explore More Software Engineering Skills→
adryanevadryanev
2

review-pr

Post inline code review comments on GitHub pull requests using the gh CLI.

Community
Advanced
matt-rileymatt-riley
1

github-cli-pr-workflow

Create, update, and monitor GitHub PRs anchored to the current head SHA.

Community
Advanced
rickyanandarickyananda
1

github-code-review

Reviews GitHub pull requests and local diffs for security and quality issues.

Community
Advanced
mczkzkmczkzk

pr-review

Review GitHub pull requests and diffs for bugs, regressions, security risks, and missing tests.

Community
Advanced