review-pr

Identify security risks and backward-compatibility issues in pull requests using CLAUDE.md guidelines.

3.9k|557|Updated Jul 30, 2021
One-click install
npx skills add https://github.com/mysticaltech/terraform-hcloud-kube-hetzner --skill review-pr-mysticaltech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/mysticaltech/terraform-hcloud-kube-hetzner/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/mysticaltech/terraform-hcloud-kube-hetzner --skill review-pr-mysticaltech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are prone to missing security risks, malicious changes, and backward-compatibility issues. This Skill provides a structured, CLAUDE.md-guided review workflow to surface these concerns during pull-request reviews.

Core Features & Use Cases

  • CLAUDE.md-guided checks for breaking changes, malicious patterns, and backward compatibility.
  • Risk classification and actionable recommendations to maintain security and quality.
  • Deterministic workflow from PR fetch to final recommendation, ensuring repeatable reviews.

Quick Start

Review a PR by running the assistant with the PR number to trigger a security-focused evaluation.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I identify security risks and backward-compatibility issues in a pull request?

A security-focused PR review detects malicious patterns and breaking changes by applying CLAUDE.md guidelines to fetch and analyze pull request code, classifying risks into actionable recommendations.

How do I automate detecting malicious patterns and breaking changes during code review?

You can detect malicious patterns and breaking changes by triggering a security-focused PR evaluation, which fetches the pull request and applies CLAUDE.md guidelines to classify risks.

What is the best way to ensure repeatable and deterministic security checks across pull requests?

To ensure repeatable security checks across pull requests, use a deterministic review workflow that applies CLAUDE.md guidelines to fetch code changes and generate consistent risk classifications.

Does this pull request review workflow require any specific dependencies or environment setup?

No external dependencies are required; this pull request review workflow operates independently, requiring only the pull request number to trigger a security-focused evaluation applying CLAUDE.md guidelines.

Can I use this to review code changes for backward compatibility across different projects?

Yes, this workflow reviews code changes for backward compatibility across projects where security and maintainability matter, applying CLAUDE.md guidelines to detect breaking changes and malicious patterns.

What limitations should I expect when assessing risk signals in pull requests?

Limitations when assessing risk signals in pull requests include reliance on CLAUDE.md guidelines for deterministic checks, meaning detection is bounded by the configured malicious patterns and backward-compatibility rules.