🔍
QualityHTML

Deep Audit

by pedrohcgs

Deep Audit is a Quality skill for Claude Code, published by pedrohcgs in claude-code-my-workflow.

1.5K stars2.9K forkson pedrohcgs/claude-code-my-workflowAdded 2026/08/19+1% in starsRepository updated 2026/06/10
academic-writingcausal-inferenceclaude-codeclaude-code-skillseconometricseconomicslatexquartoreproducible-researchresearch-workflow
Install in seconds
Install Deep Audit
Copy Deep Audit into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/deep-audit ~/.claude/skills/deep-audit

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/deep-audit/SKILL.md in pedrohcgs/claude-code-my-workflow
Installs to
~/.claude/skills/deep-audit
Collection
One of 25 skills cataloged from this repository
Category
Quality1354 skills

What Deep Audit does

Deep Audit launches four parallel specialist agents to find factual errors, code bugs, count mismatches, and cross-document inconsistencies across a repository, then fixes all issues and loops until clean. Use it after broad changes, before releases, or when asked to audit or check everything.

Deep Audit is cataloged under Quality on DirSkills. Deep Audit comes from a repository tagged academic-writing, causal-inference, claude-code, claude-code-skills and econometrics.

Documentation

README

/deep-audit — Repository Infrastructure Audit

Run a comprehensive consistency audit across the entire repository, fix all issues found, and loop until clean.

When to Use

  • After broad changes (new skills, rules, hooks, guide edits)
  • Before releases or major commits
  • When the user asks to "find inconsistencies", "audit", or "check everything"

Workflow

PHASE 0: Mechanical checks (run FIRST, cheap, deterministic)

Before spawning agents, run the mechanical parity checks:

python3 scripts/check-skill-integrity.py --verbose

This catches four classes of bug that agent-based audits have historically missed:

This is the opening of the README. Read the full README on GitHub.

Commands Deep Audit provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /deep-audit
  • /interview-me

Frequently asked about Deep Audit

  • What else does pedrohcgs publish alongside Deep Audit?

    Deep Audit is one of 25 skills that DirSkills catalogs from pedrohcgs/claude-code-my-workflow, the repository it ships in. Its siblings there include Audit Reproducibility, Capture Environment and Checkpoint. Each one is a separate skill with its own page in this directory, installs the same way Deep Audit does, and is maintained by pedrohcgs in that same repository. The rest of the collection is listed on the pedrohcgs/claude-code-my-workflow page.

  • How does Deep Audit compare to other Quality skills?

    Deep Audit ranks #645 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Deep Audit against them. Open each page to compare what they document and how they install.

More from pedrohcgs/claude-code-my-workflow

Deep Audit is one of 25 skills cataloged on DirSkills from pedrohcgs/claude-code-my-workflow.

See all 25 skills
🔍
2w ago

Audit Reproducibility

Audit Reproducibility compares numeric claims in a manuscript against actual analysis outputs and reports PASS/FAIL per claim against tolerance thresholds. Use it before submission, before releasing a replication package, or after a major revision to catch mismatches between the paper and the code.
Quality
1.5K2.9K
🧰
2w ago

Capture Environment

Capture Environment snapshots a project’s software stack for a replication package, including language versions, package locks, seeds, and RNG settings. Use it before releasing or handing off analysis code so others can rebuild the same environment.
DevOps
1.5K2.9K
📌
2w ago

Checkpoint

Checkpoint saves a structured state snapshot before stopping or handing off, capturing the active plan, recent decisions, file pointers with line numbers, open questions, and next actions. Use it before a break, model switch, or collaborator handoff when you need to resume quickly.
AI Engineering
1.5K2.9K
🤝
2w ago

Coauthor Brief

Coauthor Brief generates a Markdown handoff brief for co-authors or future selves, summarizing git changes, artifact status, open questions, and local reproduction steps. Use it when onboarding a collaborator, sending a co-author the repo, or doing a periodic sync.
Automation
1.5K2.9K
🚀
2w ago

Commit, PR, and Merge

Commit, PR, and Merge stages changes, verifies quality gates, commits with a descriptive message, creates a pull request, and merges to main when the user explicitly asks to commit or ship changes.
Automation
1.5K2.9K
📄
2w ago

Compile Beamer LaTeX Slides

Compile Beamer LaTeX Slides compiles Beamer LaTeX slide decks using XeLaTeX with a 3-pass build sequence (xelatex, bibtex, xelatex twice). Use it when the user asks to compile, build slides, rebuild PDF, run latex, or render tex files in Slides/*.tex.
Automation
1.5K2.9K