security-review

Review git diffs and pull requests for security-relevant changes with inline advisory comments.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/akoita/agent-toolkit --skill security-review-akoita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/akoita/agent-toolkit/tree/main/plugins/claude/security/skills/security-review
Command: npx skills add https://github.com/akoita/agent-toolkit --skill security-review-akoita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review often misses security issues that static rule engines cannot express, such as broken authorization, IDOR, business-flow flaws, and invariant violations. This Skill performs a fast, diff-scoped security review that produces falsifiable, inline findings a human can verify in seconds. ## Core Features & Use Cases - Diff-scoped analysis: Establishes the correct diff with git diff origin/main...HEAD (merge-base, triple-dot) and filters to added, copied, modified, and renamed files. - Prioritized review checklist: Focuses on authorization/IDOR, multi-step business flows, invariants, trust boundaries, SSRF, new dependencies, authentication changes, secrets handling, and CI workflow files. - OWASP Top 10:2025 coverage frame: Uses the 2025 list as an end-of-pass coverage check, with the API Security Top 10 cited as 2023. - Falsifiable inline output: Each finding is anchored to a file:line with severity, confidence, CWE, and a concrete exploit path; silence is a valid result when nothing security-relevant changed. - Use Case: Before merging a pull request that adds a new invoice endpoint, run this review to catch a missing tenant-ownership check and receive an inline comment citing the exact line and attack path. ## Quick Start Review the security impact of my current branch's diff against main and return inline findings with severity and confidence.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I review a pull request for security issues?▼

Fetch the base branch and diff with triple-dot syntax, `git diff origin/main...HEAD`, so you review only what the branch changed. Then prioritize authorization checks, business flows, invariants, and trust boundaries, and write one inline comment per finding anchored to a file:line.

What is the difference between a diff security review and a repository security audit?▼

A diff review is fast, narrow, and advisory, targeting only the changes in a branch or pull request. A whole-repository audit is a separate, deeper activity handled by a dedicated audit skill; this review explicitly does not serve as a blocking gate.

Why use triple-dot instead of two-dot git diff for pull request review?▼

Triple-dot diffs against the merge base and shows only what the branch changed. Two-dot also includes everything that landed on main since branching, which wastes review effort on unrelated code and produces confusing comments.

Can an AI security review act as a blocking merge gate?▼

No. Run-to-run instability makes a model verdict unfit to block merges, and a gate that fails inconsistently loses authority. The review is advisory: it reports findings with severity and confidence and lets a human decide.

What should a security review report when a diff has no issues?▼

Say so plainly and stop, for example stating that the diff touches only formatting or test fixtures with no trust boundary or authorization change. Manufacturing an informational finding to look thorough makes reviews get ignored.