Exhaustive Systems Analysis

Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.

49 stars 10 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add petekp/claude-code-setup --skill exhaustive-systems-analysis
Manual install
git clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/exhaustive-systems-analysis ~/.claude/skills/exhaustive-systems-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Exhaustive Systems Analysis

Use this skill for full-system correctness work. The job is to map the system, identify the highest-risk behaviors, prove or refute concrete failure hypotheses, and leave behind a report another engineer can act on without re-reading the whole codebase.

## Failure Modes To Prevent

1. Surface-level audits that scan files without following behavior end-to-end
2. False certainty: reporting suspicions as bugs without enough evidence
3. Context drift across large audits with many subsystems
4. Cosmetic reviews that miss the real correctness and ship-readiness risks

## Operating Mode

- Default to `chat-first` output. Return findings inline unless the user asks for docs or the audit clearly needs multi-session artifacts.
- Switch to `artifact mode` for large or resumable audits. Use `docs/audit/` or `.claude/docs/audit/`, matching the repo's existing conventions.
- Do not start fixing code while auditing unless the user explicitly asks for fixes. This skill is for diagnosis, proof, and prioritization.

## Workflow

### 0. Calibrate The Audit

Before reading deeply, write a one-screen scope brief using the template in `references/templates.md`.

Capture:
- system or area under review
- user-visible workflows or contracts that matter most
- likely high-risk surfaces: state, side effects, concurrency, auth, persistence, external integrations
- out-of-scope areas
- output mode: `chat-first` or `artifact mode`
Read the full skill on GitHub

Details

Skill name
exhaustive-systems-analysis
Path
skills/exhaustive-systems-analysis/SKILL.md
License
MIT
Repo updated
26 October 2026

FAQ

What does the Exhaustive Systems Analysis skill do?

Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.

How do I install the Exhaustive Systems Analysis skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill exhaustive-systems-analysis. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Exhaustive Systems Analysis popular?

It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.

Related skills

Catch Up

49

petekp/claude-code-setup

Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.

AI, LLMs & Agents10

Clean Copy

49

petekp/claude-code-setup

Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.

Writing & Content10

Code Comments

49

petekp/claude-code-setup

Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.

Software Development10

Latent Potential

49

petekp/claude-code-setup

First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this become", "is there a bigger play here", "how do I make this valuable or impactful", "assess this project", "strategic review", "where should t

Software Development10

Dayz Modding

23

StarDZ-Team/Dayz-Modding-Skills

ALWAYS use when touching ANY DayZ file (.c, config.cpp, mod.cpp, .layout, types.xml) or discussing DayZ modding, Enforce Script, or the Enfusion engine. Activate even if the user does not explicitly mention DayZ — if the code imports DayZ classes (PlayerBase, EntityAI, ItemBase, MissionServer), uses DayZ APIs (GetGame(), Class.CastTo(), ScriptRPC), or references DayZ patterns (modded class, CfgPatches, requiredAddons), this skill MUST be loaded. Covers 40+ critical gotchas, complete engine API across 20+ systems, mod architecture, RPC networking, GUI widgets, performance optimization, and prof

Software Development11

Timovi Tech Lead

49

theminimalcreator/timovi

Tech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.