security-review

Reviews delivered code for OWASP-aligned vulnerabilities and produces a severity-ranked findings report.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/gener8v/gener8v.claude-skills --skill security-review-gener8v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/gener8v/gener8v.claude-skills/tree/main/skills/security-review
Command: npx skills add https://github.com/gener8v/gener8v.claude-skills --skill security-review-gener8v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Delivered code often ships with injection vectors, authentication gaps, exposed secrets, or compliance violations that only surface after deployment. This Skill performs a code-level security review of a delivered ticket, cross-references compliance constraints, and records findings with severities, attack scenarios, and explicit risk-acceptance decisions. ## Core Features & Use Cases - OWASP-informed code review: Checks input validation, authentication and authorization, data protection, configuration, dependencies, cryptography, and logging against the OWASP Top 10:2025. - Severity-ranked findings with attack scenarios: Every Medium-or-higher finding includes a plausible attack scenario; compliance constraint (CC-XXX) violations are automatically elevated to Critical, and hardcoded secrets are always Critical. - Two-phase workflow: A findings phase that can run in a fresh reviewer-agent context in parallel with code and quality reviews, followed by an interactive resolution phase where findings are fixed, deferred, or accepted as documented risks. - Use Case: After a ticket touching user input or authentication is delivered, run the review to produce a report at .gener8v/changes/<change-slug>/reviews/, then resolve each finding with the user and record approved remediations in the delivery record. ## Quick Start Run a security review on the delivered ticket by saying: security review TICKET-007 in the current change.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I run a security review on delivered code?▼

Invoke the skill with a delivered ticket, such as 'security review TICKET-007', optionally naming the change with 'in <change-slug>'. If no delivery record exists, you can point directly at code files and the review degrades gracefully.

What does an OWASP code-level security review check?▼

It checks input validation, authentication and authorization, data protection, configuration security, dependencies, cryptography, and logging against the OWASP Top 10:2025. Every Medium-or-higher finding must include a plausible attack scenario.

How are compliance constraint violations handled in a security review?▼

Violations of compliance constraints (CC-XXX) from the constraints analysis are automatically elevated to Critical severity regardless of exploitability, because compliance is requirement-based rather than risk-based.

Can a security review run without a delivery record?▼

Yes, you can point the skill directly at code files to review. Missing constraints or technical design artifacts skip those checks and are noted in the report rather than blocking the review.

When should I use security-review instead of an OWASP Top 10 review?▼

Use security-review for a code-level review of a specific delivered ticket. Use owasp-top10-review for a whole-codebase posture assessment, and owasp-llm-top10-review for prompt-injection risk in LLM features.

Why does Orchestrate still list my security review as missing?▼

The state script looks for exactly `.gener8v/changes/<change-slug>/reviews/<area-slug>-ticket-nnn-security-review.md` with a lowercase ticket slug inside the ticket's change. Move or rename the file; the top-level reviews directory is never searched for ticket reviews.