codebase-audit
全面代码库审计 — 自适应并行深度分析（前后端契约、数据完整性、异常处理/安全、架构/技术债、配置/缓存），输出按严重程度排序的统一报告和修复路线图。Use when user asks to audit, analyze, or review an entire codebase for design issues, find hidden bugs, check architecture health, or asks '全面审查', '代码库审计', '分析设计问题', 'audit codebase', 'health check', '有哪些问题'. Also trigger when user asks to find silent degradation, data flow breakpoints, type mismatches between frontend and backend, or wants to understand technical debt across a project.
npx skills add majiayu000/claude-skill-registry --skill codebase-audit --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.
# Codebase Audit — Adaptive Deep Analysis A comprehensive codebase audit that adapts its agent configuration to the project's tech stack. Each agent uses opus for maximum thoroughness. Results are compiled into a unified report sorted by severity with a phased repair roadmap. ## Core Principles 1. **Opus only** — All audit agents MUST use `model="opus"`. This is non-negotiable. Smaller models miss subtle cross-file issues. 2. **Depth over breadth** — Fewer agents with broader scope and deeper analysis beats many shallow agents. Each agent should trace issues across file boundaries. 3. **Adaptive** — Agent count and focus areas vary by project type. Don't waste an agent on "frontend rendering" for a backend-only project. ## When to Use - User asks to audit/review/analyze an entire codebase - User wants to find hidden bugs, silent degradation, or design inconsistencies - User asks about technical debt, architecture health, or "what's broken" - Before a major refactor or after inheriting an unfamiliar codebase - Periodic health check (monthly/quarterly) ## Workflow ### Phase 0: Tech Stack Detection Detect the project's tech stack to determine the agent configuration: ``` Detection che
- Core Principles
- When to Use
- Workflow
- Phase 0: Tech Stack Detection
- Phase 1: Launch Agents (Adaptive)
- Phase 2: Compile Unified Report
- Deduplication
- Severity Classification
- Stack-Specific Patterns
What does the codebase-audit skill do?
全面代码库审计 — 自适应并行深度分析（前后端契约、数据完整性、异常处理/安全、架构/技术债、配置/缓存），输出按严重程度排序的统一报告和修复路线图。Use when user asks to audit, analyze, or review an entire codebase for design issues, find hidden bugs, check architecture health, or asks '全面审查', '代码库审计', '分析设计问题', 'audit codebase', 'health check', '有哪些问题'. Also trigger when user asks to find silent degradation, data flow breakpoints, type mismatches between frontend and backend, or wants to understand technical debt across a project.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill codebase-audit --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.