audit

Runs code-quality and security audits on a codebase, path, or branch diff.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill audit-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/cursor/.claude/skills/audit
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill audit-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing an entire codebase for quality issues, security vulnerabilities, and test gaps is slow and inconsistent. This Skill automates a structured audit that combines code review, security analysis, test health checks, and tooling verification into a single severity-ranked report. ## Core Features & Use Cases - Scoped Audits: Audit the entire codebase, a specific directory or file, or a branch's diff against the default branch. - Multi-Phase Review: Coordinates a judge subagent for code quality, a security-reviewer subagent for vulnerabilities, plus test coverage and lint/format checks. - Severity-Ranked Report: Produces a Markdown audit report grouping findings by Critical, High, Medium, and Low severity with recommended actions. - Use Case: Before merging a release branch, run the audit on the branch diff to catch security issues and untested critical paths, then address the Critical and High findings first. ## Quick Start Ask the agent to run /audit on the current branch to get a severity-ranked code-quality and security report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run a security audit on my codebase?▼

Run /audit with no arguments to audit the entire codebase, or pass a path or branch name to narrow the scope. The audit spawns a security-reviewer subagent and reports findings grouped by severity.

How to audit only the changes in a branch?▼

Pass the branch name to the audit command, for example /audit feature-x. The audit reviews that branch's diff against the default branch instead of the full codebase.

What does the audit report include?▼

The report contains a summary count of Critical, High, Medium, and Low findings, detailed findings grouped by severity, and a list of recommended actions. It also covers test health, coverage targets, and lint/format status.

Does the audit check test coverage and linting?▼

Yes. Phase 4 runs the project's test command and checks coverage against the configured target, while Phase 5 verifies format and lint commands are clean and flags dependencies with known CVEs.

When should I use a full audit versus a scoped audit?▼

Use a full codebase audit for periodic health checks or before major releases. Use a path- or branch-scoped audit for faster feedback on a specific change, since large scopes take longer to review.