security-review

Identify and document security gaps across codebase modules using structured checklists.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ashtonian/llm-init --skill security-review-ashtonian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/security-review
Command: npx skills add https://github.com/ashtonian/llm-init --skill security-review-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security reviews are often manual, time-consuming, and inconsistent. This skill provides a structured, repeatable approach to audit a codebase for vulnerabilities, misconfigurations, and policy violations, reducing risk and improving confidence before release.

Core Features & Use Cases

  • Systematic, checklist-driven assessment across input handling, authentication, data protection, dependencies, logging, and infrastructure.
  • Generates a structured Findings report suitable for engineering and security teams.
  • Use Case: security review of a web service with multiple integration points and data flows.

Quick Start

Run a systematic security review against the target codebase using the provided checklist and generate a structured report.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a systematic security audit on my codebase?

A systematic security audit involves a structured review across input validation, authentication, data protection, dependencies, error handling, and infrastructure. This process identifies common vulnerability patterns and policy violations to generate a reproducible findings report.

What does a structured code review for security vulnerabilities include?

A structured security review covers input handling, authentication, data protection, dependency risks, logging, and infrastructure misconfigurations. It uses a checklist-driven approach to assess common vulnerability patterns and signal risks to engineering and security teams.

Can I use a checklist-driven security review for web services with multiple integration points?

Yes, checklist-driven security reviews are designed for web services with multiple integration points and complex data flows. The structured assessment scales across modules to evaluate input validation, authentication, and data protection regardless of codebase size.

How do I document security gaps and policy violations for my development team?

Documenting security gaps requires generating a structured Findings report based on a checklist-driven assessment. This report details vulnerability patterns, policy compliance issues, and risk signals suitable for both engineering and security teams.

What is the best way to ensure reproducibility when analyzing codebase risks?

Reproducibility in codebase risk analysis is achieved by following a frontmatter-defined scope and using predefined checklists. This ensures consistent evaluation of input validation, authentication, data protection, and infrastructure across multiple audits.

Does static analysis for security review cover dependencies and infrastructure misconfigurations?

Yes, static analysis for security review explicitly covers dependencies and infrastructure alongside input validation, authentication, and error handling. It identifies misconfigurations and policy violations to reduce risk and improve release confidence.