Forge-Security-Review

Review code changes and dependency manifests for security defects against OWASP standards.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-security-review-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Security-Review
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/05-Security/Forge-Security-Review
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-security-review-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security weaknesses in code changes and third-party dependencies often slip into production because reviews are ad-hoc and untraceable. This Skill provides a structured, standards-based security review process that produces severity-classified, evidence-linked findings that flow into defect management. ## Core Features & Use Cases - Secure Code Review: Inspect implementation changes for injection flaws, broken access control, authentication defects, insecure deserialisation, and sensitive-data exposure against OWASP Top 10, ASVS, and Proactive Controls. - Dependency Vulnerability Assessment: Check dependency manifests and lockfiles against known-vulnerability sources, flagging vulnerable, abandoned, or licence-incompatible components. - Risk Triage and Routing: Classify confirmed findings by severity, gate critical issues before merge, and record accepted-risk decisions in a decision log. - Use Case: Before merging a pull request that touches authentication logic, run this Skill to review the diff against OWASP controls, assess the updated dependency manifest, and route confirmed findings to defect management with full evidence. ## Quick Start Ask the AI to perform a Forge security review of the current code changes and dependency manifest against the OWASP standards and produce severity-classified findings.

Frequently Asked Questions about Forge-Security-Review

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

FAQPage Schema
How do I perform a secure code review against OWASP standards?▼

Scope the change and weight effort toward trust-boundary and sensitive-data code, then inspect it against OWASP Top 10, ASVS, and Proactive Controls. Record each finding with location, exploitability condition, and severity, then validate and triage confirmed issues.

How to check dependencies for known vulnerabilities?▼

Review dependency manifests and lockfiles against known-vulnerability sources, flagging vulnerable, abandoned, or unexpected components. Run this on a regular cadence and immediately when a relevant CVE is disclosed.

What is the difference between security review and security testing?▼

Security review statically inspects code and dependencies for weaknesses against standards like OWASP ASVS. Security testing validates behaviour at runtime through execution and scanning, which is handled by a separate Forge-Security-Testing skill.

When should a security review not be used?▼

Do not use it as a substitute for threat modelling, runtime verification, or a preliminary surface-level scan of an existing codebase. It also does not fix defects itself; resolution belongs to development agents.

How are accepted security risks handled in a review?▼

When a finding is waived, the decision, owner, and compensating controls are recorded in a decision log. Risk acceptance is always owned by humans and never assumed by the review process itself.