quick-audit

Audit a small code scope for security issues with a checklist.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill quick-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-audit
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/subagent-system/skills/quick-audit
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill quick-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and surface security issues in a small code scope (1-5 files or a single module) without running the full pipeline, enabling rapid risk awareness.

Core Features & Use Cases

  • Spawns a single read-only audit agent with an injection/crypto/auth checklist and severity-rated findings.
  • Supports specifying a target path and an optional focus to prioritize concerns.
  • Ideal for pre-PR quick reviews or quick security checks of a module or folder.

Quick Start

Audit the given path quickly for security concerns, optionally focusing on a specific area.

Frequently Asked Questions about quick-audit

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

FAQPage Schema
How do I run a quick security audit on a small code scope before submitting a PR?

Run a quick security audit on a small code scope by targeting 1-5 files or a single module. It surfaces security issues rapidly for pre-PR risk awareness without running a full pipeline.

Can I focus my code review on specific security areas like injection or authentication?

You can focus your code review by passing an optional focus parameter to prioritize specific concerns. The audit agent uses a security checklist covering injection, crypto, and authentication.

What is the best way to identify security issues in a single module without running the full pipeline?

The best way to identify security issues without a full pipeline is using a targeted audit agent. It parses the path input, lists files, applies a security checklist, and outputs structured findings.

Does this targeted security audit work for large codebases or just small file scopes?

This targeted security audit is designed for small code scopes of 1-5 files or a single module. It is optimized for quick, focused reviews rather than scanning large codebases.

How are security findings structured during a focused pre-PR code review?

Security findings during a focused pre-PR code review are output as structured, severity-rated results. The single read-only audit agent evaluates the specified path and delivers organized risk findings.

Why use a quick focused audit instead of a full security pipeline for post-change analysis?

Use a quick focused audit for post-change analysis to gain rapid risk awareness without the overhead of a full pipeline. It provides immediate, severity-rated feedback on recent module modifications.