code-review

Audits source code for security vulnerabilities using grep pattern matching across multiple languages.

632|86|Updated Apr 29, 2023
One-click install
npx skills add https://github.com/yaklang/yaklang --skill code-review-yaklang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yaklang/yaklang/tree/main/common/ai/aid/aireact/skills/code-review
Command: npx skills add https://github.com/yaklang/yaklang --skill code-review-yaklang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing large codebases for security flaws is slow and error-prone. This Skill systematizes source code security auditing by using grep-based pattern matching to locate dangerous function calls, sensitive data flows, and known vulnerability patterns across a project. ## Core Features & Use Cases - Multi-language vulnerability detection: Covers 30+ CWE types including SQL injection, command injection, XSS, SSRF, path traversal, deserialization, XXE, and SSTI across Java, Golang, PHP, Python, C/C++, and JavaScript. - Phased audit workflow: Scans by vulnerability category, then verifies each hit by reading surrounding code context to check for input filtering, parameterized queries, and escaping. - Configuration and crypto checks: Detects hardcoded credentials, weak algorithms (MD5, DES, ECB), insecure TLS settings, and risky CORS/Cookie configurations. - Use Case: Point the Skill at a legacy PHP project to find all mysql_query calls with concatenated user input, verify each finding in context, and produce a severity-ranked audit report with remediation advice. ## Quick Start Audit the project at /path/to/project for security vulnerabilities and write a severity-ranked report of all confirmed findings.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I audit source code for security vulnerabilities with grep?▼

Run phased grep scans with regexp patterns targeting one vulnerability class at a time, such as SQL injection sinks or command execution functions. Then read the surrounding code of each hit to verify whether input filtering or parameterized queries are present.

What vulnerability types does this code audit cover?▼

It covers over 30 CWE types including SQL injection, command injection, XSS, SSRF, path traversal, insecure deserialization, XXE, SSTI, open redirect, hardcoded credentials, weak cryptography, and C/C++ memory safety issues like buffer overflow.

Which programming languages are supported for security review?▼

The audit patterns cover Java, Golang, PHP, Python, C/C++, and JavaScript. Each language has dedicated grep patterns for its dangerous APIs, such as Runtime.exec in Java, exec.Command in Go, and pickle.loads in Python.

How are grep findings verified before reporting?▼

Each grep hit is verified by reading 20-50 lines of surrounding code to check for input filtering, parameterized queries, escaping functions, and whether the data source is user-controlled. Only confirmed risks are written into the final report.

What are the limitations of grep-based code auditing?▼

Grep pattern matching cannot trace data flow across files or understand runtime behavior, so it may produce false positives and miss indirect vulnerabilities. Findings require manual context verification, and complex taint analysis needs dedicated static analysis tools.