security-review-subagent

Detect security issues in pull request diffs using a six-check brief.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/razorpay/ai-playbook --skill security-review-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-subagent
Source: https://github.com/razorpay/ai-playbook/tree/main/skills/security-review-subagent
Command: npx skills add https://github.com/razorpay/ai-playbook --skill security-review-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams catch security-shaped issues in a PR by running a bounded, fresh-context security review and returning structured findings the reviewer can act on.

Core Features & Use Cases

  • Per-PR security judgement: Reviews the branch diff against a canonical six-check brief, with citations to file/line and a suggested fix.
  • Deterministic subagent contract: Uses a fixed brief template with placeholders for branch/base to keep results consistent run-to-run.
  • Coverage for common PR risk surfaces: Flags redlines, capability creep, untrusted-input misuse, output exposure, injection-vulnerable shapes, and unscoped capabilities.

Quick Start

Run the Claude Code skill by saying: start the security review on this branch.

Frequently Asked Questions about security-review-subagent

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

FAQPage Schema
How do I run a security review on a pull request diff?

Run an automated security review on a pull request diff by executing the skill against your branch and base to receive a structured Markdown artifact with file/line citations and suggested fixes. It applies a fixed six-check brief to detect security redlines.

What security issues should I check for when adding MCP connector grants or agent invocations?

When adding MCP connector grants or agent invocations, check for capability creep, untrusted-input misuse, output exposure, injection-vulnerable shapes, and unscoped capabilities. A fixed six-check security brief flags these specific risk surfaces in the PR diff.

Can I automate prompt injection detection for untrusted input ingestion in my code?

Yes, you can automate prompt injection detection for untrusted input ingestion by running a fresh-context subagent against your PR diff. It flags injection-vulnerable shapes and untrusted-input misuse with structured findings and suggested fixes.

Does security review work on documentation-only or CSS-only pull requests?

No, security review does not work on documentation-only or CSS-only changes. The skill explicitly declines doc-only and CSS-only PRs, applying its six-check brief only to branches that introduce agent invocations, external surfaces, or untrusted-input ingestion.

What is a deterministic subagent contract for structured security findings?

A deterministic subagent contract for structured security findings uses a fixed brief template with placeholders for branch and base, keeping results consistent run-to-run. It outputs a Markdown artifact with one section per finding, including citations and a deterministic summary header.

How do I generate a Markdown security report with file and line citations from a branch diff?

Generate a Markdown security report from a branch diff by running the security review skill. It produces a structured artifact with one section per finding, including file/line citations, risk levels, suggested fixes, and a deterministic summary header.