security-review

Detect security flaws in codebases via static analysis with OWASP Top 10 coverage.

17|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/insightflo/claude-impl-tools --skill security-review-insightflo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/insightflo/claude-impl-tools/tree/main/plugin/skills/security-review
Command: npx skills add https://github.com/insightflo/claude-impl-tools --skill security-review-insightflo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects security flaws in codebases with static analysis and surfaces actionable remediation guidance to prevent deploying vulnerable software.

Core Features & Use Cases

  • OWASP Top 10 coverage across common risk areas (A01–A10) and guidance for remediation.
  • Evidence-rich reports with precise file paths, line numbers, and context to support triage and fixes.
  • Pre-flight and PR integration, enabling security checks before merges and during audits.

Quick Start

Run the security scan on your repository to surface findings and recommended mitigations.

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 static security scan to check for OWASP Top 10 vulnerabilities?

To run a static security scan, the tool analyzes your codebase to identify OWASP Top 10 vulnerabilities. It surfaces findings with evidence and remediation guidance, producing a structured report with precise file paths and line numbers.

Can I automate vulnerability detection during pull request reviews?

Yes, you can automate vulnerability detection during pre-deployment and PR reviews. The static analysis identifies security flaws before merges, providing evidence-rich reports to support triage and fixes.

Does static analysis detect exposed secrets and dependency risks in my code?

Static analysis detects exposed secrets and dependency risks alongside OWASP Top 10 coverage. It scans across multiple languages to surface these findings with actionable remediation guidance.

What is the best way to generate an audit report with file paths and line numbers for security flaws?

The best way to generate an audit report is using static analysis that produces structured findings with file_path:line evidence. This format is suitable for audit integration and artifact generation during ongoing security audits.

How do I fix security flaws identified during a codebase audit?

To fix security flaws identified during an audit, the tool provides actionable remediation guidance for each finding. Evidence-rich reports include precise context to support triage and guide your fixes.

What is static security scanning and when do I need it for my software deployment?

Static security scanning is the process of identifying security flaws in a codebase without running it. You need it during pre-deployment and ongoing audits to prevent deploying vulnerable software.