skills.rest
Sir-chawakorn
Sir-chawakornCOMMUNITY
Explore all skills by this author →
GitHub

security-review

Audits git diffs for injection, access control flaws, hardcoded secrets, and dependency issues during code reviews.

9|3|Updated Jun 13, 2026
Search Tags:#code review#security#vulnerability#audit#injection#devsecops
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill security-review-sir-chawakorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/security-review
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill security-review-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the risk of introducing vulnerabilities during development by providing a structured, diff-based security audit process that catches common flaws before code is merged.

Core Features & Use Cases

  • Vulnerability Detection: Identifies injection risks, access control gaps, hardcoded secrets, and insecure dependencies.
  • Context-Aware Review: Focuses specifically on changed code hunks to ensure high-signal, low-noise security analysis.
  • Use Case: Before merging a pull request that modifies authentication logic or handles user-provided file paths, use this Skill to verify that all inputs are sanitized and access controls are correctly implemented.

Quick Start

Run the security-review skill to audit the current git diff for potential vulnerabilities and dependency issues.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I audit code changes for security vulnerabilities before merging?▼

A security review of code changes focuses on changed code hunks to systematically trace source-to-sink data flows, detecting injection risks, access control flaws, and hardcoded secrets before code is merged.

What is source-to-sink tracing in code security audits?▼

Source-to-sink tracing in a security audit tracks untrusted user input as it flows through application code to verify proper sanitization, ensuring no vulnerable execution paths reach sensitive operations.

Can I check for hardcoded secrets and insecure dependencies in a pull request review?▼

Yes, a pull request security review can detect hardcoded secrets and insecure dependencies by applying context-aware security auditing directly to the changed code hunks and external libraries.

Does this security audit work on pre-commit checks involving authentication logic?▼

Yes, security auditing works on pre-commit checks involving authentication logic by verifying that user inputs are properly sanitized and access controls are correctly implemented before delivery.

What is the best way to reduce false positives during a vulnerability audit?▼

The best way to reduce false positives during a vulnerability audit is to perform context-aware analysis focused specifically on changed code hunks, ensuring high-signal, low-noise security findings.

When do I need a diff-based security audit instead of a full codebase scan?▼

You need a diff-based security audit when reviewing pull requests or pre-commit changes to verify modified authentication logic and file path handling, ensuring high-signal vulnerability detection without full codebase noise.

Related Skills

Explore More Software Engineering Skills→
kaochenlongkaochenlong

spectra-audit

Audit git diffs for security sharp edges using the spectra CLI.

Community
Advanced
huseyindenizhuseyindeniz
15

security-audit

Analyze TypeScript/JavaScript source code for hardcoded secrets and unsafe patterns.

Community
Advanced
brenordvbrenordv

security

Audit software systems for security vulnerabilities and regulatory compliance.

Community
Advanced
JoaovsalesJoaovsales
1

security-scan

Scan recently changed code for OWASP-aligned security vulnerabilities before merge or deployment.

Community
Intermediate