Agent skill · Security

audit

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Path: plugins/elixir-phoenix/skills/audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Project Health Audit Comprehensive project-wide health assessment using 5 parallel specialist subagents. ## Usage ``` /phx:audit # Full audit (default) /phx:audit --quick # 2-3 minute pulse check /phx:audit --focus=security # Deep dive single area /phx:audit --focus=performance /phx:audit --since abc123 # Incremental audit since commit /phx:audit --since HEAD~10 # Audit last 10 commits ``` ## When to Use - **Quarterly** health checks - **Before major releases** - **After large refactors** - **New team member onboarding** (understand codebase health) ## Iron Laws 1. **Wait for ALL agents before synthesizing** — Partial results create misleading health scores because cross-category correlations get missed 2. **Scope agent prompts to specific directories** — Vague prompts like "analyze the codebase" produce generic findings that waste tokens and miss real issues 3. **Never compare scores across projects** — Scoring methodology depends on project size and maturity; only track trends within the same project 4. **Quick mode before full mode** — Run `--quick` first to catch compile/test failures before spending tokens on 5 parallel agents ## Subagent Architecture Spawn 5 specialists in

What's inside
Steps it walks through
  1. Usage
  2. When to Use
  3. Iron Laws
  4. Subagent Architecture
  5. Workflow
  6. Step 1: Create Task List and Spawn All 5 Auditors (Parallel)
  7. Step 2: Collect Results
  8. Step 3: Compress Findings
  9. Step 4: Calculate Health Score
  10. Step 5: Generate Report
  11. Output Format
  12. Quick Mode (--quick)
  13. Focus Mode (--focus=area)
  14. Incremental Mode (--since <commit>)
Ships with 2 files
  • references/architecture-checks.md
  • references/scoring-methodology.md
More from claude-elixir-phoenix
All skills →
About this skill
What does the audit skill do?

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill 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 oliver-kriska/claude-elixir-phoenix, a repository with 515 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.

Keep going