audit

Review code for security vulnerabilities, performance issues, and quality problems with severity-ranked findings.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill audit-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/audit
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill audit-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing code for security flaws, performance bottlenecks, and quality issues is slow and inconsistent. This Skill provides a structured audit checklist that catches SQL injection, XSS, hardcoded secrets, N+1 queries, and code complexity problems in a single pass. ## Core Features & Use Cases - Security Scanning: Detects SQL injection, XSS, CSRF, command injection, path traversal, hardcoded credentials, and broken access control. - Performance Analysis: Identifies N+1 queries, unbounded loops, memory leaks, and blocking calls in async code. - Quality Review: Flags cyclomatic complexity above 10, deep nesting, magic numbers, missing types, and dead code. - Use Case: Before merging a pull request that touches authentication logic, run an audit to get a severity-ranked list of issues (HIGH/MEDIUM/LOW) with file and line references, plus concrete code fixes for the top three problems. ## Quick Start Audit the authentication module for security vulnerabilities and performance issues, then list findings by severity with fixes for the top issues.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit code for security vulnerabilities?

Run a structured security audit that checks for SQL injection, XSS, CSRF, command injection, path traversal, and hardcoded credentials. Findings are grouped by severity (HIGH, MEDIUM, LOW) with file and line references for each issue.

How to find hardcoded secrets and API keys in code?

Scan the codebase for hardcoded credentials, API keys embedded in source files, and committed .env files. These are flagged as security findings so secrets can be moved to a secrets manager or environment variables.

What performance issues can a code audit detect?

A code audit detects N+1 database queries, unbounded loops, memory leaks, and blocking calls inside async functions. Each finding includes the file and line number so you can locate and fix the bottleneck directly.

Does the audit provide fixes for the issues it finds?

Yes, the audit provides concrete code fixes for the top three HIGH or MEDIUM severity issues. Fixes are delivered as code only, without lengthy explanations, so they can be applied directly.

What are the limitations of a static code audit?

A static audit cannot detect runtime-only issues such as live race conditions under load or vulnerabilities dependent on deployed configuration. Combine it with dynamic testing and dependency scanning for full coverage.