code-audit

Audit codebases for bugs, security flaws, and performance issues.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cenjie/skills --skill code-audit-cenjie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/cenjie/skills/tree/main/skills/code-audit
Command: npx skills add https://github.com/cenjie/skills --skill code-audit-cenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct a broad, risk-first audit to uncover bugs, security vulnerabilities, performance bottlenecks, architectural weaknesses, and production-readiness gaps across a repository or feature area so teams can prioritize fixes that materially reduce user and business risk.

Core Features & Use Cases

  • Risk-first discovery: Build a concise Repo Mental Map identifying runtimes, entry points, auth, data flows, and high-risk surfaces before deep inspection.
  • Evidence-backed findings: Map each issue to exact files, routes, or flows with severity, confidence, impact, and minimal remediation steps.
  • Focused deep dives: Perform targeted audits for security, performance, architecture, or launch-readiness and produce core and extended deliverables such as Executive Summary, Top Risks, and sequenced action plans.
  • Use case: Use for pre-release launch checks, acquisition due diligence, cross-repo security sweeps, or a maintainability health check of a large service.

Quick Start

Run a repository-wide code audit focused on security, correctness, maintainability, and production readiness and return a Repo Mental Map, Executive Summary, Top Risks, and detailed Findings.

Frequently Asked Questions about code-audit

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

FAQPage Schema
How do I perform a security audit and risk assessment on my codebase?

To perform a codebase security audit, build a Repo Mental Map to identify runtimes, auth, and data flows, then deep inspect for security flaws, performance issues, and architectural weaknesses to produce prioritized findings with severity, confidence, and remediation steps.

What does a production-readiness check look for in a repository?

A production-readiness check identifies launch gaps by mapping high-risk surfaces and architectural weaknesses across a repository, yielding an Executive Summary, Top Risks list, and sequenced action plans to ensure the codebase is ready for release.

Can I run a targeted security audit on just a feature module instead of the full repo?

Yes, you can run a focused deep dive on specific feature modules or targeted security surfaces. The audit produces evidence-backed findings mapped to exact files, routes, and flows with impact analysis and minimal remediation steps.

How do I prioritize codebase risks found during an architecture review?

To prioritize codebase risks found during an architecture review, map each issue to exact files with severity, confidence, and impact ratings. This risk-first approach produces a prioritized findings list to help teams focus on fixes that materially reduce business risk.

What is the best way to prepare for an acquisition due diligence code audit?

The best way to prepare for an acquisition due diligence code audit is to run a risk-first repository-wide sweep. This uncovers security vulnerabilities, performance bottlenecks, and architectural weaknesses, delivering an Executive Summary and Top Risks to evaluate business risk.

When should I not use an automated repo analysis for finding bugs?

Automated repo analysis for finding bugs may not be suitable if you need immediate hotfix patches for isolated incidents rather than a comprehensive architectural assessment. It is designed for broad risk-first discovery and sequenced action plans, not single-line corrections.