skills.rest
martin-janci
martin-janciCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Analyzes pull-request diffs and generates inline comments with verdicts.

Updated Jan 30, 2026
Search Tags:#github#static-analysis#code-review#pull-request#conventional-comments#review-automation
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill code-review-martin-janci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill code-review-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review diffs in pull requests to identify bugs, security issues, and code quality concerns, enabling faster, higher-quality merges.

Core Features & Use Cases

  • Conventional Comments: generate structured inline feedback using standard labels (issue, suggestion, nitpick, question, praise).
  • Verdict-driven review: supports APPROVE, COMMENT, or REQUEST_CHANGES based on finding severity.
  • Codebase access checks: validates code usage with Read, Grep, and Glob patterns and maintains a per-PR state.
  • JSON-ready output: exports findings for integration with CI or PR comment tooling.

Quick Start

Provide a structured review of the given PR diff with inline comments and a final verdict.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate pull request reviews to catch bugs and security issues?▼

Automate pull request reviews by analyzing PR diffs to identify bugs, security issues, and code quality problems. This generates structured inline feedback and a final verdict to enable faster, higher-quality merges.

How does conventional comments work for structured code review feedback?▼

Conventional comments for code review feedback use standard labels like issue, suggestion, nitpick, question, and praise. This structured approach categorizes inline feedback clearly so developers understand the severity and intent of each remark.

Can I use automated code review across diverse repositories and team workflows?▼

Automated code review works across diverse repositories and team workflows by applying to GitHub PRs or raw code diffs. It maintains a per-PR state and validates code usage with Grep, Read, and Glob patterns regardless of the repository structure.

How do I gate pull request merges based on static analysis severity?▼

Gate pull request merges based on static analysis severity by using verdict-driven review outputs. The review pipeline generates APPROVE, COMMENT, or REQUEST_CHANGES verdicts depending on the severity of the identified code quality problems.

Does the code review automation output JSON for CI integration?▼

Code review automation outputs a JSON-friendly format containing all findings and the final verdict. This structured export allows direct integration with CI pipelines or automated PR comment tooling.

What's the best way to verify code usage during a PR diff review?▼

The best way to verify code usage during a PR diff review is using Grep, Read, and Glob patterns. These tools validate actual codebase usage and usage patterns to ensure the review feedback is accurate and context-aware.

Related Skills

Explore More Software Engineering Skills→
aarushlohitaarushlohit

zen-review

Review pull request changes for correctness, security, performance, and quality.

Community
Advanced
TeamSloppyTeamSloppy
26

github-code-review

Automate structured code reviews of local changes and GitHub PRs.

Official
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
JitsusamaJitsusama
6

conventional-comments

Format code review feedback with Conventional Comments labels and decorations.

Community
Basic