security-review

Reviews branch diffs, PRs, or working trees adversarially for exploitable vulnerabilities before merge.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/patrickserrano/lacquer --skill security-review-patrickserrano
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/patrickserrano/lacquer/tree/main/core/skills/security-review
Command: npx skills add https://github.com/patrickserrano/lacquer --skill security-review-patrickserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes that touch trust boundaries β€” authentication, input parsing, secrets handling, CI workflows β€” can introduce vulnerabilities that pass functional tests but fail under adversarial conditions. This Skill performs a structured security review of a diff before merge, catching injection, path traversal, secret leakage, privilege escalation, and fail-open guards that reviewers commonly miss. ## Core Features & Use Cases - Adversarial Diff Review: Treats the change as hostile until proven safe, tracing untrusted input from source to sink across shell, SQL, YAML, and LLM instruction contexts. - Trust-Boundary Fan-Out: Splits large changes into per-boundary review passes (auth, input parsing, secrets, CI/exec, file I/O) and dedupes findings. - Verify-Before-Reporting: Requires each finding to state the exact triggering inputs and resulting wrong behavior, defaulting to "refuted" when uncertain to avoid false positives. - Use Case: Before merging a PR that adds a CI workflow running on a self-hosted runner, ask for a security review to check whether untrusted fork code could execute with privileged permissions or whether third-party actions are unpinned. ## Quick Start Ask the AI to security review the current branch diff against main and report ranked findings with file, line, severity, and suggested fixes.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I security review a pull request before merging?β–Ό

Run an adversarial review over the PR diff obtained via gh pr diff, tracing untrusted input from source to sink. Report only findings tied to a concrete failure scenario, ranked by severity with file:line and a suggested fix.

What vulnerabilities should I check for in a code diff?β–Ό

Check for injection of untrusted input into shell, SQL, YAML, or LLM contexts; path traversal and symlink escapes; secrets leaked to artifacts or process tables; over-privileged CI runners and unpinned actions; and fail-open guards that silently pass on error.

Can this review large changes with multiple trust boundaries?β–Ό

Yes. Large changes are fanned out into one reviewer per trust boundary β€” auth, input parsing, secrets, CI/exec, and file I/O β€” and the findings are deduplicated afterward, since a single pass tends to miss cross-cutting issues.

How does the review avoid false positive findings?β–Ό

Each candidate finding must state the exact inputs and state that trigger it plus the resulting wrong behavior. If a nearby check already prevents it, the finding is dropped, and uncertain cases default to refuted.

When should I run a fresh-eyes security review as a separate agent?β–Ό

Run a separate agent given only the diff, with no implementation context, for high-risk changes. This catches bug classes that the implementer's own tests and context-aware review tend to miss.