security-review

Review code, configuration, and infrastructure for exploitable weaknesses with severity-ranked evidence.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill security-review-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/security-review
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill security-review-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security-relevant changes often ship without a systematic check for exploitable weaknesses, exposed secrets, or authorization defects. This Skill performs a bounded, evidence-backed security review of a diff, component, or repository and produces severity-ranked findings with the smallest correct fix for each. ## Core Features & Use Cases - Scoped Weakness Detection: Maps the attack surface of a defined scope and reviews injection surfaces, authentication and authorization paths, network posture, identity configuration, supply chain, and data handling against OWASP Top 10 categories. - Secret Exposure Handling: Classifies discovered secret material as confirmed, test-only, or false positive, records its location and rotation requirement, and never copies the secret value into reports. - Structured Reporting: Emits schema-validated JSON and Markdown reports where every finding cites a file path, an exploitable path or hardening classification, independent severity and confidence ratings, and enumerated unassessed scope. - Use Case: Before merging a pull request that adds a new API endpoint, run this Skill on the diff to confirm the endpoint enforces authorization, rank any gap found, and route remediation to the audit-plan-remediation workflow. ## Quick Start Review the changes in this pull request for security weaknesses and produce a severity-ranked findings report.

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 vulnerabilities before merging?

Define the pull request diff as the review scope, then the Skill maps its attack surface and checks authorization, injection surfaces, secrets, and supply chain. Each finding includes a file path, exploitable path, severity, confidence, and the smallest correct fix.

What does a security code review cover beyond OWASP Top 10?

Beyond injection and access control categories, the review covers secret exposure in source and workflows, server-side request forgery, certificate validation, over-permissive identity roles, unpinned dependencies, lock-file integrity, and logging of privileged actions.

When should I use security-review instead of a full code audit?

Use security-review for bounded, security-focused passes on a diff, component, or repository before merging or releasing security-relevant changes. Use audit-code instead when you need a whole-repository quality assessment rather than exploit-focused findings.

Can a security review tool detect exposed secrets without leaking them?

Yes. Findings classify each secret hit as confirmed, test-only, or false positive and record only its location and rotation requirement. The secret value is never copied into the report, and confirmed live secrets trigger immediate escalation.

What are the limitations of a read-only security review?

A read-only review does not execute exploits, probe live systems, or modify security controls, so it proves weaknesses through code evidence rather than active exploitation. Scope that cannot be assessed is enumerated explicitly with the reason in the report.