skill CX Codex

full-audit — Claude Code skill: what it does, how to install

Q: How do I install full-audit in Claude Code?

Run `npx skills add undeadlist/claude-code-agents --skill full-audit -a claude-code` in your terminal.

Q: Where are the audit reports stored?

Each agent writes its markdown file into `.claude/audits/`, producing files such as `AUDIT_CODE.md` and `API_TEST_REPORT.md`. The consolidated action plan is saved as `.claude/audits/FIXES.md`.

Runs 11 audit agents in parallel across your repository and consolidates issues into a prioritized action plan. Designed for pre-release inspections or routine weekly health checks.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add undeadlist/claude-code-agents --skill full-audit -a claude-code

Open on GitHub

What full-audit does

This skill orchestrates a two-phase audit for your repository. The first phase runs in parallel. It triggers 11 specialized agents at once to check runtime bugs, code quality, OWASP rules, infrastructure configs, performance, and API endpoints. Each agent writes its report directly into .claude/audits/.

Once all audits finish, the skill spawns fix-planner. This agent reads every AUDIT_*.md file and creates .claude/audits/FIXES.md with prioritized tasks. You need the individual auditor agents installed beforehand, or the workflow cannot generate reports. After reviewing the plan, you can run code-fixer on critical P1 defects and verify them with test-runner.

What it helps with

audit an entire codebase in parallel before releases
scan code for OWASP security vulnerabilities
consolidate multi-agent findings into a prioritized FIXES.md
validate API endpoints and generate API_TEST_REPORT.md

Example prompts for the agent

Run a full audit across the entire codebase
Execute all parallel audit agents and generate a fix plan
Perform a repository health check and save findings to .claude/audits/

How to install full-audit

1Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill full-audit -a claude-code

2Manually: put the files in place

~/.claude/skills/full-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/full-audit/

1Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill full-audit -a codex

2Manually: put the files in place

.agents/skills/full-audit/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill full-audit -a cursor

2Manually: put the files in place

.cursor/skills/full-audit/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install undeadlist/claude-code-agents full-audit

2Manually: put the files in place

.github/skills/full-audit/SKILL.md

1Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill full-audit -a gemini-cli

2Platform CLI

gemini skills install https://github.com/undeadlist/claude-code-agents --path skills/full-audit

Manually: put the files in place

.devin/skills/full-audit/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill full-audit -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about full-audit

How do I install full-audit in Claude Code?

Run npx skills add undeadlist/claude-code-agents --skill full-audit -a claude-code in your terminal.

What does the full-audit skill do?

It initiates 11 audit agents in parallel to inspect code quality, security vulnerabilities, runtime bugs, and configuration. Then fix-planner reads all reports and compiles a prioritized FIXES.md file.

Where are the audit reports stored?

Each agent writes its markdown file into .claude/audits/, producing files such as AUDIT_CODE.md and API_TEST_REPORT.md. The consolidated action plan is saved as .claude/audits/FIXES.md.

Source text

SKILL.md · MIT

---
name: full-audit
description: Run all 11 audit agents in parallel, then consolidate findings with fix-planner
---

# Full Audit Workflow

Run a comprehensive audit of the entire codebase. Use before major releases or as a weekly health check.

## Phase 1: Parallel Audit

Spawn ALL of the following agents **in parallel** (single response with multiple Task calls):

| Agent | Output File | Focus |
|-------|-------------|-------|
| `code-auditor` | `.claude/audits/AUDIT_CODE.md` | Code quality |
| `bug-auditor` | `.claude/audits/AUDIT_BUGS.md` | Runtime bugs |
| `security-auditor` | `.claude/audits/AUDIT_SECURITY.md` | OWASP deep scan |
| `doc-auditor` | `.claude/audits/AUDIT_DOCS.md` | Documentation gaps |
| `infra-auditor` | `.claude/audits/AUDIT_INFRA.md` | Infrastructure config |
| `ui-auditor` | `.claude/audits/AUDIT_UI_UX.md` | UI/UX and accessibility |
| `db-auditor` | `.claude/audits/AUDIT_DB.md` | Database performance |
| `perf-auditor` | `.claude/audits/AUDIT_PERF.md` | Performance issues |
| `dep-auditor` | `.claude/audits/AUDIT_DEPS.md` | Dependency health |
| `seo-auditor` | `.claude/audits/AUDIT_SEO.md` | SEO optimization |
| `api-tester` | `.claude/audits/API_TEST_REPORT.md` | API validation |

Each agent targets the project's source code. Provide each with a prompt like:
```
Audit [target directory]. Save report to [output file].
```

## Phase 2: Consolidation

After **all** auditors complete, spawn:
- `fix-planner` - Read all `.claude/audits/AUDIT_*.md` files and create `.claude/audits/FIXES.md` with prioritized action items

## Post-Audit Actions

1. Review `FIXES.md` - Prioritize based on your timeline
2. Run `code-fixer` - Implement P1 (critical) fixes
3. Run `test-runner` - Verify fixes work
4. Re-audit affected areas if needed

improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. 1,141,062installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs codebase-design Matt Pocock This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write. 850,344installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs

From the same set6

release-prep Runs a full audit, fixes critical bugs, validates deploy readiness and writes the release PR. Useful right before shipping a version to production. CX Codex +1 ★ 149repo stars pre-deploy Runs parallel checks on builds, environment variables, and dependencies before deploying to production. CX Codex +1 ★ 149repo stars pre-commit Review changed code and run the full test suite before a commit. Get a clear pass-or-fail verdict with the issues that need attention. CX Codex +1 ★ 149repo stars new-feature Runs a new feature through four ordered steps: failing tests first, then code, then the full suite. Handy when regressions are the thing you keep missing. CX Codex +1 ★ 149repo stars bug-fix This skill guides an agent through reproducing a bug with a test, applying a focused fix, and checking for regressions. Use it when a bug report needs a verifiable fix. CX Codex +1 ★ 149repo stars