sfermanelli-review-pr

Review pull request diffs with structured risk and actionable feedback.

1|Updated Mar 19, 2026

Search Tags:#feedback #quality #review #diff #code-review #pull-request

Ready to run

npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-review-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sfermanelli-review-pr
Source: https://github.com/sebafermanelli/sfermanelli-skills/tree/main/sfermanelli-review-pr
Command: npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing pull requests and code changes can be tedious and inconsistent. This skill provides a structured, senior-engineer level approach to PR reviews to improve code quality and maintainability.

Core Features & Use Cases

Structured Review Process: read context, diffs, tests, and architecture implications to provide focused, actionable feedback.
Quality Gatekeeping: identify critical defects, potential risks, and improvement opportunities to help teams merge confidently.
Use Case: when you want a thorough review of a PR, a diff, or a merge readiness check, across languages and repositories.

Quick Start

Provide the PR diff or link and I will deliver a senior-engineer style review with actionable feedback.

Frequently Asked Questions about sfermanelli-review-pr

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

FAQPage Schema

How do I review a pull request like a senior engineer?▼

To review a pull request like a senior engineer, provide the PR diff or link to receive a structured assessment. The process evaluates context, tests, and architecture implications to deliver focused, actionable feedback for confident merging.

What is the best way to structure code review feedback for a PR?▼

The best way to structure code review feedback is by separating critical defects from actionable improvements. This approach assesses potential risks and architecture implications to help teams merge confidently while maintaining code quality and maintainability.

Can I perform a merge readiness check across different programming languages?▼

Yes, you can perform a merge readiness check across different programming languages and repositories. The review applies a consistent framework to identify critical defects and improvement opportunities regardless of the specific language used.

How do I identify critical risks and defects in a code diff?▼

To identify critical risks and defects in a code diff, the review reads context, tests, and architecture implications. It enforces a structured framework that categorizes feedback into critical defects versus actionable improvements for quality gatekeeping.

When do I need a structured framework for pull request reviews?▼

You need a structured framework for pull request reviews when manual checks become tedious and inconsistent. Applying senior-engineer rigor ensures thorough quality gatekeeping by identifying critical defects, potential risks, and improvement opportunities before merging.