Agent skill · data analytics · aiskillstore
audit
Run comprehensive codebase audit for gaps, deprecated code, TODOs, FIXMEs, architectural anti-patterns, type issues, and code smells. Use when user asks to audit code, find issues, check code quality, or identify architectural problems.
Why this skill is useful
Provides a structured methodology for comprehensive codebase audits, identifying specific quality issues and architectural patterns that the AI wouldn't generate on its own.
What it needs
Requires eslint, typescript installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Codebase Audit Instructions Perform a comprehensive, systematic audit of the codebase to identify quality issues, architectural problems, and technical debt. Phase 1: Discovery & Planning 1. Identify scope - Determine which files/directories to audit based on user request 2. Create comprehensive file list - Use Glob to find all relevant files 3. Initialize todo list - Create a todo with one item per file to audit 4. Set up audit report - Create structured markdown report at .audit/audit-report-[timestamp].md Phase 2: Automated Analysis Run automated tools to supplement manual review: TypeScript compiler diagnostics ESLint (if configured) Grep for common patterns: TODO, FIXME, HACK, XXX, @deprecated Phase 3: Systematic File Review For EACH file in the todo list: 1. Read and analyze the file thoroughly 2. Check for issues in these categories: Deprecations: Deprecated APIs, patterns, or code marked for removal TODOs/FIXMEs: Unfinished work or known issues Architectural anti-patterns: God objects/classes Circular dependencies Tight coupling Violation of SOLID principles Inconsistent patterns Type issues: Use of any or unknown Missing type annotations Incorrect type usage Type casts that hide issues Code smells: Duplicated code Long functions/classes Complex conditionals Dead code Magic numbers/strings Poor naming 3. Assign severity to each finding: CRITICAL: Breaks functionality, security issues, data corruption risks HIGH: Architectural violations, major maintainability issues MEDIUM: Code smells, minor anti-patterns, missing types LOW: Style issues, minor TODOs, cosmetic improvements 4. Check for cross-file patterns - As you review, note patterns that appear across multiple files 5. Update report - Add findings to the structured report 6. Mark file as completed in todo list Phase 4: Cross-File Analysis After reviewing all individual files: 1. Identify systemic patterns - Issues that appear across multiple files 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/audit