adversarial-pr-review

Review GitHub pull request diffs for exploitable security changes.

3|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/equaltoai/lesser-body --skill adversarial-pr-review-equaltoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-pr-review
Source: https://github.com/equaltoai/lesser-body/tree/main/.agents/skills/adversarial-pr-review
Command: npx skills add https://github.com/equaltoai/lesser-body --skill adversarial-pr-review-equaltoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform a security-first review of a pull request by analyzing the real diff at a pinned head SHA, so you can spot exploitable changes before they are merged.

Core Features & Use Cases

  • Threat-model the diff: Examine changed files for attack surfaces such as auth, parsing, secrets, network calls, and resource limits.
  • Refute before reporting: Test every candidate finding for reachability, existing guards, and pre-existing context so only durable issues survive.
  • Comment-only PR review: Produce inline review threads and a summary without approving, requesting changes, or merging.
  • Use case: A maintainer asks for a hostile-eyes review of a dependency or auth change in a governed GitHub repository.

Quick Start

Review PR 42 in the governed repository, pin the current head SHA, and post only surviving security findings as a comment-only review.

Frequently Asked Questions about adversarial-pr-review

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

FAQPage Schema
How do I perform a security review on a GitHub pull request?

Perform a security review on a GitHub pull request by analyzing the real diff at a pinned head SHA to spot exploitable changes. This process examines changed files for attack surfaces like auth, parsing, secrets, network calls, and resource limits before merging.

What is adversarial threat modeling for pull request diffs?

Adversarial threat modeling for pull request diffs is a review technique that generates security candidates based on exploitable changes, then attempts refutation by testing reachability, existing guards, and pre-existing context so only durable issues survive reporting.

Can I use an automated security review to comment on a PR without approving it?

Yes, you can use an automated security review to post comment-only feedback on a PR. It produces inline review threads and a summary without approving, requesting changes, or merging the pull request.

Does pull request security analysis work on changes touching cryptography and authz?

Yes, pull request security analysis applies to governed GitHub repositories when changes touch auth, parsing, secrets, network access, cryptography, or resource safety, ensuring exploitable modifications are flagged before integration.

What is the best way to find security bugs in a dependency or auth change?

The best way to find security bugs in a dependency or auth change is to run a hostile-eyes review that grounds on a pinned head SHA, applies diff-aware threat modeling, and refutes each candidate finding before reporting.

Why does my security review report false positives on pull requests?

Security reviews report false positives on pull requests when findings skip refutation. Testing each candidate for reachability, existing guards, and pre-existing context ensures only durable, exploitable issues survive the final reporting stage.