exhaustive-systems-analysis
Perform comprehensive, deep analysis of a system and its subsystems to identify bugs, race conditions, stale documentation, dead code, and correctness issues. Use when asked to "audit this system", "exhaustive analysis of X", "analyze for correctness", "root out issues in...", "deep dive into...", "verify this code is correct", "find bugs in...", or when reviewing agent-written code for production readiness. Automatically decomposes systems into subsystems, applies appropriate analysis checklists, and produces structured findings with severity classification.
npx skills add majiayu000/claude-skill-registry --skill exhaustive-systems-analysis --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.
# Exhaustive Systems Analysis Systematic audit methodology for rooting out latent issues in codebases, particularly agent-written code that needs verification before production use. ## Core Principles 1. **Subsystem isolation** — Analyze each subsystem separately to prevent context pollution 2. **Evidence-based findings** — Every issue must cite specific code locations 3. **Severity-driven prioritization** — Critical issues first, cosmetic issues last 4. **Assume all issues will be fixed** — Don't hedge; be direct about what's wrong ## Workflow ### Phase 1: System Decomposition Before analysis, map the system's subsystems. Auto-discover by: 1. **Read project structure** — Identify major modules, packages, or directories 2. **Trace data flow** — Follow how data enters, transforms, and exits 3. **Identify side effects** — File I/O, network, database, IPC, state mutations 4. **Map dependencies** — Which subsystems depend on which Output a subsystem table: ```markdown | # | Subsystem | Files | Side Effects | Priority | |---|-----------|-------|--------------|----------| | 1 | Lock System | lock.rs | FS: mkdir, rm | High | | 2 | API Layer | api/*.rs | Network, DB | High | | 3 | Config P
- Core Principles
- Workflow
- Phase 1: System Decomposition
- Phase 2: Sequential Analysis
- Phase 3: Consolidation
- Analysis Checklists
- Stateful Systems (files, databases, caches, locks)
- APIs & Network (HTTP, gRPC, WebSocket, IPC)
- Concurrency (threads, async, channels, locks)
- UI & Presentation (views, components, templates)
- Data Processing (parsers, transformers, validators)
- Configuration & Setup (config files, environment, initialization)
- Severity Classification
- Finding Format
What does the exhaustive-systems-analysis skill do?
Perform comprehensive, deep analysis of a system and its subsystems to identify bugs, race conditions, stale documentation, dead code, and correctness issues. Use when asked to "audit this system", "exhaustive analysis of X", "analyze for correctness", "root out issues in...", "deep dive into...", "verify this code is correct", "find bugs in...", or when reviewing agent-written code for production readiness. Automatically decomposes systems into subsystems, applies appropriate analysis checklists, and produces structured findings with severity classification.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill exhaustive-systems-analysis --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.