review-security

Audit code for vulnerabilities, hardcoded secrets, and insecure patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and helps remediate security vulnerabilities, secrets, and unsafe coding patterns within your codebase, reducing the risk of breaches and exploits.

Core Features & Use Cases

  • Vulnerability Scanning: Detects common security flaws like injection, broken authentication, and sensitive data exposure.
  • Secret Detection: Flags hardcoded API keys, passwords, and other secrets that should not be in source control.
  • Dependency Auditing: Checks for known vulnerabilities in project dependencies.
  • Use Case: Before deploying a new feature that handles user authentication, run this Skill to ensure no critical security gaps were introduced.

Quick Start

Run a security audit on the code that has been staged for commit.

Frequently Asked Questions about review-security

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

FAQPage Schema
How do I run a security audit on staged code changes before committing?

To run a security audit on staged code, you can scope the review to your staged changes. This identifies vulnerabilities, hardcoded secrets, and insecure patterns while providing severity classifications and remediation guidance before you commit.

Can this scan for hardcoded secrets and API keys in my codebase?

Yes, secret detection is a core feature that flags hardcoded API keys, passwords, and other sensitive credentials in your codebase. This prevents unsafe secrets from being committed to source control and reduces breach risks.

Does the security audit check project dependencies for known CVEs?

Yes, the security audit includes dependency auditing to check your project dependencies for known CVEs. It scans your libraries to identify vulnerable components and helps you remediate them to secure your codebase.

What types of vulnerabilities does a code security audit look for?

A code security audit prioritizes detecting critical vulnerability types like injection flaws, broken authentication, and sensitive data exposure. It comprehensively scans for insecure coding patterns across your entire codebase or scoped changes.

What is the best way to find insecure coding patterns in my project?

The best way to find insecure coding patterns is to conduct a comprehensive security audit scoped to your entire codebase. This proactively identifies unsafe patterns, classifies findings by severity, and provides specific remediation guidance.