peer_review

Reviews academic documents and code using structured evaluation frameworks and checklists.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill peer-review-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer_review
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/peer_review
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill peer-review-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing academic papers, technical documents, and code changes without a consistent methodology leads to missed issues, vague feedback, and inconsistent quality standards across reviewers. ## Core Features & Use Cases - Structured Evaluation Framework: Assess clarity, methodology, validity, originality, and completeness of documents using a standardized rubric. - Code Review Checklist: Verify functionality, code quality, security, and performance with ready-made checklist items covering DRY principles, input validation, and memory leaks. - Three-Phase Review Workflow: Follow a preparation, review, and approval process aligned with Google Engineering Practices and Conventional Comments. - Use Case: When reviewing a pull request, use the workflow to check that the PR description answers what, why, and how to test, then leave tagged comments like nit: or blocking: before approving the merge. ## Quick Start Review this pull request using the peer review checklist and provide constructive feedback with severity ratings.

Frequently Asked Questions about peer_review

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

FAQPage Schema
How do I write constructive code review feedback?

Constructive code review feedback uses specific suggestions instead of criticism, such as proposing a try-catch for a potential error case. Use conventional comment tags like nit, suggestion, or blocking, and address the code rather than the author.

What should a code review checklist include?

A code review checklist should cover functionality, code quality, security, and performance. Key items include edge case handling, DRY principle adherence, input validation, SQL injection risks, and memory leak detection.

How do I evaluate an academic paper for peer review?

Evaluate an academic paper across five areas: clarity, methodology, validity, originality, and completeness. Summarize strengths and areas for improvement, then give a recommendation of accept, minor revisions, major revisions, or reject.

What are the phases of a pull request review process?

The pull request review process has three phases: preparation by the reviewee with self-review and context, the review itself covering clarity, security, and performance, and approval requiring green CI checks and resolved blocking comments.

When should I use this instead of a dedicated code review tool?

Use this for academic and technical document review plus general code review guidance. For deep automated code analysis, the skill description directs you to a dedicated code-review skill instead.