pr-review

Analyze pull request code changes for style, bugs, security, and test coverage.

5|Updated Jan 14, 2025
One-click install
npx skills add https://github.com/timmo001/dotfiles --skill pr-review-timmo001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/timmo001/dotfiles/tree/main/agents/.config/opencode/skills/pr-review
Command: npx skills add https://github.com/timmo001/dotfiles --skill pr-review-timmo001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers systematically analyze and review code changes, ensuring standards compliance and identifying issues efficiently.

Core Features & Use Cases

  • Code Quality Evaluation: Checks if the PR follows style guides and best practices.
  • Issue Identification: Detects potential bugs, security risks, and performance concerns.
  • Documentation and Test Review: Assesses whether documentation and test coverage are adequate.
  • Use Case: A developer submits a PR; use this Skill to generate a detailed review focusing on code consistency and potential problems.

Quick Start

Use the pr-review skill to analyze the latest pull request on the project.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I check code quality and security in a pull request?

Code review for pull requests analyzes code changes to identify style adherence, potential bugs, security issues, and testing coverage across multiple files. It provides actionable feedback to ensure code quality and standards compliance.

What is the best way to automate bug detection during git code reviews?

Bug detection during code reviews involves analyzing pull request changes to identify potential bugs and performance concerns. It provides actionable feedback for ensuring code quality and systematic issue identification across multiple lines and files.

Does this code review process assess test coverage and documentation?

Yes, the code review process assesses test coverage and documentation. It evaluates whether documentation is adequate and testing coverage is sufficient, alongside checking style adherence and identifying security risks in the pull request.

Can I review multiple files and lines in a pull request systematically?

Yes, you can systematically review multiple files and lines in a pull request. The analysis operates across all changed files and lines, providing actionable feedback to aid developers in conducting thorough code reviews.

What security issues can I identify when analyzing pull request changes?

Analyzing pull request changes helps identify potential security risks and performance concerns. It detects security issues alongside checking style adherence and potential bugs, aiding developers in thorough and systematic code reviews.