code-review

Review GitHub pull request diffs and metadata with severity-based verdicts.

4|5|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fartybobo/farty-bobo --skill code-review-fartybobo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/fartybobo/farty-bobo/tree/main/skills/code-review
Command: npx skills add https://github.com/fartybobo/farty-bobo --skill code-review-fartybobo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, time-consuming effort of understanding diffs, CI results, and discussion threads so you can deliver precise, actionable reviews quickly.

Core Features & Use Cases

  • Authentication safeguards: it checks GitHub CLI auth before touching any data so you never proceed without permission.
  • Context-first evaluation: it fetches PR metadata, diffs, comments, and related Jira tickets to understand intent before flagging anything.
  • Structured findings: it classifies issues by severity, calls out praises or questions, and wraps up with a consolidated verdict that includes inline comment guidance.

Quick Start

Ask the skill to review PR #42 and summarize correctness, design, and CI findings with a 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 for correctness and design?

Automating pull request reviews involves analyzing PR diffs and metadata to surface meaningful feedback. This skill fetches GitHub PR details, classifies issues by severity, and delivers a consolidated verdict covering correctness, design, and CI checks.

Can I review GitHub CI checks and conversation threads together before merging?

Yes, you can review GitHub CI checks and conversation threads together. The skill runs gh commands to fetch diffs, checks, and discussions, consolidating findings into a structured compliance assessment before merge.

Do I need GitHub CLI authentication to analyze PR diffs?

Yes, GitHub CLI authentication is required to analyze PR diffs. The skill explicitly checks GitHub CLI auth before fetching any data, ensuring you never proceed without proper repository permissions.

What is the best way to structure code review feedback with severity levels?

The best way to structure code review feedback is by classifying issues by severity. This skill categorizes findings, highlights praises or questions, and wraps up with a consolidated verdict that includes inline comment guidance.

How does diff analysis handle related Jira tickets and PR metadata?

Diff analysis handles related Jira tickets and PR metadata by fetching context first. The skill collects this information to understand the intent behind the pull request before flagging any correctness or design issues.