pr-review

Automate Azure DevOps pull request review with security checklists and risk scoring.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pr-review-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pr-review-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pull request reviews often miss critical security issues, lack consistency, and provide unstructured feedback that is hard to act on. This Skill automates comprehensive analysis with mandatory security checklists, risk-based mode escalation, and structured findings that ship as inline comments.

Core Features & Use Cases

  • Smart-Default Mode: Runs full security pass, risk scoring, and content-type detection automatically without requiring flags.
  • Security Checklist (S1-S15): Mandatory scan for recurring security pitfalls including auth bypass, secret leakage, injection, and supply chain risks.
  • Risk-Based Escalation: Auto-promotes to three-role adversarial council or cross-model copilot verification based on blast radius and diff content.
  • Content-Type Awareness: Detects doc, skill, rule, template, spec, infra, and code changes to calibrate severity and trigger oracle completeness checks.
  • Cross-Check Consistency: Validates same-type files against each other and cross-references prescriptive content against reference repositories.

Quick Start

Use the pr-review skill to analyze pull request 123 and post the findings inline after you confirm the authorization.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate pull request security analysis in Azure DevOps?

Automating pull request security analysis in Azure DevOps requires running a 15-point security checklist covering auth bypass, secret leakage, and injection risks. This skill executes that scan automatically, scores risk, and posts structured findings as inline comments.

What is multi-model verification for code review?

Multi-model verification for code review is an adversarial escalation process where a three-role council or cross-model copilot validates high-risk pull requests. It triggers automatically based on diff content and blast radius when standard review thresholds are exceeded.

Do I need PowerShell scripts to review Azure DevOps pull requests?

You need PowerShell scripts to review Azure DevOps pull requests using this skill because they handle PR data collection, content-type detection, and production grounding. These scripts are required dependencies for fetching repository diffs and contextual metadata.

How to calibrate code review severity based on content type?

Calibrating code review severity based on content type involves detecting whether changes target docs, infrastructure, specs, or application code. This skill automatically identifies content types to adjust severity levels and trigger oracle completeness checks for prescriptive content.

Best way to check cross-file consistency in a pull request?

Checking cross-file consistency in a pull request involves validating same-type files against each other and cross-referencing prescriptive content against reference repositories. This skill performs both checks automatically during the standard review pass.

When should pull request review escalate to council mode?

Pull request review should escalate to council mode when risk scoring indicates high blast radius or diff content exceeds standard severity thresholds. The skill auto-promotes these reviews to a three-role adversarial council for deeper multi-model verification.