review-security

Review TypeScript/JavaScript files and directories for OWASP security risks.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill review-security-hackberrybay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-security
Source: https://github.com/hackberrybay/hb-code-reviewer/tree/main/skills/review-security
Command: npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill review-security-hackberrybay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OWASP-focused security review of a file or directory to identify injection points, auth gaps, data exposure, input validation failures, and misconfigurations, enabling teams to fix critical issues before release.

Core Features & Use Cases

  • File and directory security analysis: scans a single file or an entire project to surface security issues across codebases.
  • Opus-powered thorough review: leverages a high-sensitivity model to assess risks and provide actionable findings.
  • Structured results and guidance: outputs per-file findings with an overall risk summary to guide remediation.

Quick Start

Run a security review on a file or directory by passing the path as an argument.

Frequently Asked Questions about review-security

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

FAQPage Schema
How do I review TypeScript code for OWASP security risks?

You can review TypeScript code for OWASP security risks by running an analysis on a single file or directory. It identifies injection points, auth gaps, and data exposure, returning a structured report with per-file findings and overall risk levels.

What is an OWASP-focused security review for JavaScript projects?

An OWASP-focused security review for JavaScript projects identifies injection points, authentication gaps, data exposure, and input validation failures. It provides actionable findings and an aggregated risk summary to guide remediation before release.

Can I scan an entire directory for security misconfigurations?

Yes, you can scan an entire directory for security misconfigurations. The analysis automatically excludes node_modules and build outputs, aggregating per-file findings across the full TypeScript or JavaScript project into an overall risk summary.

What's the best way to find input validation failures in my codebase?

The best way to find input validation failures is using an Opus-powered thorough code analysis. This high-sensitivity model assesses your codebase to surface validation failures and other OWASP risks, providing structured results for remediation.

Does the security analysis exclude node_modules and build outputs?

Yes, the security analysis explicitly excludes node_modules and build outputs from its scope. It focuses strictly on your source code to surface OWASP risks and misconfigurations, returning a structured report with per-file findings.