skills.rest
CarGDev
CarGDevCOMMUNITY
Explore all skills by this author →
Website𝕏@CarGDevGitHub

Code Auditor

Audit code quality by detecting dead code, complexity, duplication, and architectural smells.

Updated Jan 17, 2026
Search Tags:#architecture#refactoring#quality#complexity#code audit#tech debt#dead code
One-click install
npx skills add https://github.com/CarGDev/codetyper.cli --skill code-auditor-cargdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Code Auditor
Source: https://github.com/CarGDev/codetyper.cli/tree/main/src/skills/code-audit
Command: npx skills add https://github.com/CarGDev/codetyper.cli --skill code-auditor-cargdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high code quality by systematically identifying and reporting on issues like dead code, excessive complexity, duplication, and architectural flaws, thereby reducing technical debt.

Core Features & Use Cases

  • Dead Code Detection: Identifies unused exports, unreachable code, and commented-out blocks.
  • Complexity Analysis: Measures cyclomatic complexity, nesting depth, and function/file size.
  • Architecture Review: Detects smells such as god objects and circular dependencies.
  • Use Case: A development team can use this Skill to perform a pre-release code audit to ensure adherence to quality standards and identify potential areas for refactoring.

Quick Start

Run a comprehensive code audit on the current project directory.

Frequently Asked Questions about Code Auditor

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

FAQPage Schema
How do I detect dead code and reduce technical debt in my project?▼

An automated code audit detects dead code and reduces technical debt by identifying unused exports, unreachable code, and commented-out blocks, providing a structured report with prioritized refactoring recommendations.

How do I measure cyclomatic complexity and identify architectural smells?▼

Measuring cyclomatic complexity and identifying architectural smells involves analyzing nesting depth, function size, and detecting flaws like god objects and circular dependencies to assess overall code quality and structural integrity.

What is the best way to perform a pre-release code quality audit?▼

The best way to perform a pre-release code quality audit is systematically scanning the project directory to detect duplication, excessive complexity, and architectural flaws, ensuring adherence to quality standards before deployment.

Does code auditing require specific file system access or tools?▼

Code auditing requires read, grep, glob, and bash tools for file system analysis and pattern matching to accurately scan directories, measure complexity, and identify duplicated code segments.

Can I identify code duplication and god objects automatically?▼

You can identify code duplication and god objects automatically through an architecture review mechanism that scans for structural flaws, ensuring comprehensive technical debt reduction and prioritized refactoring.

Related Skills

Explore More Software Engineering Skills→
jubscodesjubscodes
49

gsp-doctor

Analyze GSP project .design directory for structural and configuration drift.

Community
Advanced
luispabonluispabon
6

slop-detector

Crawl codebase directories to identify technical debt and code smells.

Community
Advanced
VictorSmaniottoVictorSmaniotto

code-analyzer

Analyze PHP code for smells, complexity, duplications, and pattern violations.

Community
Intermediate
gideonshakedgideonshaked
12

codex-second-opinion

Audit Claude's output for bugs, dead code, and architectural risks via Codex.

Community
Advanced