Security Review

Run a security review checklist on code changes before merging PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Tvshreyas/DISTILL --skill security-review-tvshreyas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Security Review
Source: https://github.com/Tvshreyas/DISTILL/tree/main/.agent/skills/security-review
Command: npx skills add https://github.com/Tvshreyas/DISTILL --skill security-review-tvshreyas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a security review checklist on code changes before they ship, ensuring code quality, security, and compliance.

Core Features & Use Cases

  • Automated checks that verify type safety (TypeScript errors), linting, and vulnerability status before merging.
  • Comprehensive code-review checklist covering Authentication & Authorization, Input Handling, Data Privacy, and Infrastructure safeguards.
  • Use Case: Before merging a PR, automatically validate that API routes are secured, sensitive data is not exposed, and dependencies are scanned for vulnerabilities.

Quick Start

Review the latest code change by running the security review checklist to verify authentication, input handling, and infrastructure safeguards.

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 security review checklist on my code changes before merging?

To run a security review before merging, apply an automated checklist to your PR workflows that validates authentication, data handling, and infrastructure safeguards. This process enforces zero TypeScript errors, zero ESLint errors, and no high or critical vulnerabilities.

What does an automated code security review check for in a PR?

An automated code security review checks PRs for authentication and authorization gaps, improper input handling, data privacy exposures, and infrastructure issues. It also verifies safe handling of secrets and scans dependencies for high or critical vulnerabilities.

Can I use automated security checks to enforce zero TypeScript and ESLint errors?

Yes, you can use automated security checks to enforce zero TypeScript errors and zero ESLint errors. The review process validates type safety and linting status before merging to ensure code quality and compliance across application PR workflows.

When do I need to scan dependencies for vulnerabilities in my PR workflow?

You need to scan dependencies for vulnerabilities in your PR workflow before code changes ship. Running a security review checklist catches high and critical vulnerabilities early, ensuring sensitive data is not exposed and API routes are secured before merging.

Does this automated security review work for API routes and sensitive data handling?

Yes, the automated security review works for API routes and sensitive data handling by validating that API routes are secured and sensitive data is not exposed. It applies these infrastructure and data privacy safeguards across application PR workflows before changes ship.

What is the best way to catch authentication and infrastructure issues before shipping code?

The best way to catch authentication and infrastructure issues before shipping code is running an automated security review checklist on PRs. This enforces type safety, linting, and vulnerability scans while verifying safe handling of secrets and data privacy safeguards.