adversarial-pr-review

Dispatch adversarial subagents to review PR diffs for false-positive completion patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/telefrek/jlsm --skill adversarial-pr-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adversarial-pr-review
Source: https://github.com/telefrek/jlsm/tree/main/.claude/skills/adversarial-pr-review
Command: npx skills add https://github.com/telefrek/jlsm --skill adversarial-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects false-positive "complete" PR patterns that could lead to releasing incomplete features or functionalities, helping to ensure the integrity and correctness of pull requests.

Core Features & Use Cases

  • Adversarial Review: Conducts an adversarial subagent to analyze code diffs against specified base branches and identifies false-positive "complete" patterns.
  • Customizable Base: Can be invoked with specific PR numbers or branch names for tailored review purposes.
  • Preventative Analysis: Utilizes the skill before PR merge to catch any potential issues that may have been overlooked by the initial code reviews.

Quick Start

Review a PR for false-positive completions using /adversarial-pr-review <pr-number>

Frequently Asked Questions about adversarial-pr-review

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

FAQPage Schema
How can I catch false-positive PR completions before merging code?▼

False-positive PR completions are caught by dispatching adversarial subagents to review pull request diffs against a specified base branch, identifying incomplete features to ensure merge integrity.

What is an adversarial code review and how does it validate pull requests?▼

Adversarial code review is a preventative analysis mechanism that deploys subagents to scrutinize code diffs for false-positive completion patterns, ensuring feature integrity before a pull request is merged.

How do I run an adversarial PR review on a specific pull request number?▼

Run an adversarial PR review by invoking the skill with a specific pull request number or branch name, dispatching a subagent to analyze the diff against the base branch.

Does this pull request validation work with specific branch names instead of PR numbers?▼

Yes, pull request validation can be customized by invoking the review process with specific branch names rather than PR numbers to tailor the adversarial diff analysis.

When should I use an adversarial review instead of a standard code review?▼

Use an adversarial review as a preventative check before merging when standard code reviews may have overlooked potential issues, specifically targeting false-positive completion patterns in feature implementations.

What are the limitations of using subagents for PR feature integrity analysis?▼

PR feature integrity analysis via subagents is limited to reviewing code diffs against specified base branches and requires specific PR numbers or branch names to initiate the validation process.