Audit Full

What it does

This skill performs a thorough analysis of codebases to identify security vulnerabilities and compliance gaps. It leverages Opus 4.6 or 4.7's extended context window (up to 1 million tokens) to enable cross-file reasoning, which is often missed by traditional chunked approaches. The audit can focus on security, architecture, or dependencies within the codebase.

When to use it

• Security Audits: To proactively identify and address potential vulnerabilities in a project.
• Architecture Reviews: To assess the design and structure of a codebase for maintainability and scalability.
• Dependency Analysis: To understand and manage external libraries and their associated risks.
• Large Codebases: When dealing with projects containing approximately 50,000 lines of code (LOC) where cross-file dependencies are critical to analyze.
• Compliance Checks: To ensure a codebase adheres to specific security or regulatory standards.

Key capabilities

• Full-Codebase Analysis: Analyzes the entire project in a single pass using extended context.
• Cross-File Reasoning: Identifies vulnerabilities and architectural issues that span multiple files.
• Mode Specialization: Supports focused audits for Security, Architecture, or Dependencies.
• Dependency Analysis: Identifies and analyzes external library dependencies.
• Second Pass Analysis (Opus 4.7 only): An optional "xhigh" effort mode provides an additional cross-module pattern sweep.

Example prompts

• /ork:audit-full security - Perform a full codebase audit with a focus on security vulnerabilities.
• /ork:audit-full architecture - Conduct an architectural review of the entire project.
• /ork:audit-full dependencies - Analyze the project's external dependencies.

Tips & gotchas

• 1M Context Requirement: This skill requires a 1 million token context window (Opus 4.6 or later). Ensure CLAUDE_CODE_DISABLE_1M_CONTEXT is unset to enable full-codebase analysis.
• Task Management Mandatory: The skill relies on task creation and management for proper execution. Follow the provided TaskCreate and TaskUpdate steps precisely.
• User Intent Verification: Always begin by clarifying the audit scope using the interactive dialog (/ork:audit-full) to ensure accurate results.