review-helper

Review code diffs and report issues and questions for maintainability.

37|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/jpcaparas/skills --skill review-helper-jpcaparas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-helper
Source: https://github.com/jpcaparas/skills/tree/main/skills/skill-creator-advanced/evals/files/harness-docs/review-helper
Command: npx skills add https://github.com/jpcaparas/skills --skill review-helper-jpcaparas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review proposed code changes for correctness and maintainability, improving overall codebase quality.

Core Features & Use Cases

  • Diff Inspection: Inspect code changes in a diff format to understand the changes made.
  • Concrete Findings: Report specific issues found during the review.
  • Separation of Defects: Differentiate between verified defects and open questions for further analysis.
  • Use Case: When integrating new code into the project, this Skill can be used to review pull requests for any potential issues.

Quick Start

Review the proposed changes for the 'issue-123' pull request using the review-helper skill.

Frequently Asked Questions about review-helper

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

FAQPage Schema
How do I review code changes in a diff format for maintainability and correctness?

To review code changes in a diff format for maintainability, inspect the proposed modifications to identify specific issues, separating verified defects from open questions for further analysis without executing the code.

What is the best way to analyze pull requests for potential defects in collaborative development workflows?

Analyzing pull requests for potential defects involves carefully examining the diff details to ensure correctness, providing a structured report that differentiates between confirmed maintainability issues and open questions.

Can I identify code maintainability issues without actually executing the code?

Yes, you can identify code maintainability issues without executing code by carefully examining the change details in the diff format to ensure correctness and overall codebase quality.

How to separate verified defects from open questions during a code review?

To separate verified defects from open questions during a code review, inspect the diff to report concrete findings, categorizing specific issues that need fixing versus those requiring further analysis.

Does code review via diff inspection work for integrating new code into an existing project?

Yes, code review via diff inspection works for integrating new code by reviewing proposed changes to ensure maintainability and correctness, generating a report on any potential issues found.