comprehensive-auditor
Exhaustive multi-dimensional project auditor covering code, runtime, infrastructure, security, performance, business logic, and human processes across 12 dimensions with confidence-tracked findings and explicit blind spot documentation. Includes dead code detection (Knip/depcheck), file size/token limit analysis for AI editing compatibility, and honest system health reporting.
npx skills add majiayu000/claude-skill-registry --skill comprehensive-auditor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Comprehensive Honest Project Auditor - Maximum Coverage Edition ## Overview An exhaustive multi-dimensional project auditor that covers **code, runtime behavior, infrastructure, security, performance, business logic, and human processes**. Provides confidence-tracked findings across 12 audit dimensions with explicit blind spot documentation. ## Quick Start **Natural Language Commands:** - "Run comprehensive audit on my project" - "Audit my code for security and performance issues" - "Check my documentation accuracy and test coverage" - "Analyze my project's blind spots and confidence levels" **Slash Commands:** - `/audit-comprehensive` — Full 12-dimension audit - `/audit-comprehensive --quick` — Skip slow dimensions (runtime, performance) - `/audit-dimension security` — Single dimension deep dive - `/audit-blindspots` — Show only what can't be verified - `/audit-compare HEAD~10 HEAD` — Compare two states ## Coverage Dimensions (12 Areas) ### Dimension 1: Static Code Analysis (95% confidence) **What It Checks:** - Syntax errors, type errors, unused code - Import/export resolution - Dead code branches - Cyclomatic complexity - Code duplication **Tools Used:** - TypeScript compiler
- Overview
- Quick Start
- Coverage Dimensions (12 Areas)
- Dimension 1: Static Code Analysis (95% confidence)
- Dimension 2: Runtime Behavior Simulation (70% confidence)
- Dimension 3: Data Flow & State Management (80% confidence)
- Dimension 4: API & External Dependencies (65% confidence)
- Dimension 5: Security Vulnerabilities (60% confidence)
- Dimension 6: Performance & Scalability (55% confidence)
- Dimension 7: Documentation Accuracy (85% confidence)
- Dimension 8: Test Coverage & Quality (90% confidence)
- Dimension 9: Infrastructure & Deployment (70% confidence)
- Dimension 10: Accessibility & UX (50% confidence)
- Dimension 11: Business Logic Correctness (40% confidence)
Full audit (dry-run by default) node .claude/skills/📊\ comprehensive-auditor/scripts/orchestrator.js audit Execute safe removals only node .claude/skills/📊\ comprehensive-auditor/scripts/orchestrator.js execute --safe-only Single detector node .claude/skills/📊\ comprehensive-auditor/scripts/orchestrator.js detect --detector file-size CI mode node .claude/skills/📊\ comprehensive-auditor/scripts/orchestrator.js audit --ci Detect oversized files Custom threshold (e.g., only 20K+ tokens)
What does the comprehensive-auditor skill do?
Exhaustive multi-dimensional project auditor covering code, runtime, infrastructure, security, performance, business logic, and human processes across 12 dimensions with confidence-tracked findings and explicit blind spot documentation. Includes dead code detection (Knip/depcheck), file size/token limit analysis for AI editing compatibility, and honest system health reporting.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill comprehensive-auditor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
