Skip to main content
command CX Codex

audit-dependencies — Claude Code command: Rust dependency audit

audit-dependencies audits dependency direction in Rust projects and flags layer violations. Use it when reviewing architecture or preparing a refactor.

no license ★ 1,357 updated 2026-03-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/audit-dependencies.md
Open on GitHub

What audit-dependencies does

This command examines how a Rust codebase links its Infrastructure, Adapters, Application, and Domain layers. It extracts crate imports, reviews external dependencies, checks the domain and application boundaries, and looks for adapter implementations of application ports.

It also inspects Cargo.toml, including workspace member dependencies, and can focus on a path or module supplied as an argument. The command works through Read, Grep, Glob, and Bash. It needs a Rust project with identifiable layers; without that structure, the audit has little architectural evidence to assess.

What it helps with

  • find outer-layer imports inside the domain
  • spot direct database dependencies in application code
  • map dependency flow across Rust layers
  • check whether adapters implement application ports
  • review workspace links in Cargo.toml

Example prompts for the agent

  • Run /rust:audit-dependencies to audit dependency direction across the Rust project.
  • Focus the audit on src/application/ with /rust:audit-dependencies src/application/.
  • Use /rust:audit-dependencies to find imports that point from inner layers to outer ones.

How to install audit-dependencies

Manually: put the files in place

.claude/commands/audit-dependencies.md

Call it with /audit-dependencies. For all projects use ~/.claude/commands/

Questions about audit-dependencies

How do I install audit-dependencies in Claude Code?

Copy the command file to .claude/commands/audit-dependencies.md.

What does audit-dependencies do?

It reviews dependency direction in Rust code across the Domain, Application, Adapters, and Infrastructure layers. It also checks project and workspace dependencies in Cargo.toml.

Can audit-dependencies target one Rust module?

Yes. Add a path or module after the command, such as /rust:audit-dependencies src/application/, to limit the audit scope.

Similar slash commands

All slash commands for Backend and APIs →
audit-and-reduce-dependencies grafana audit-and-reduce-dependencies shrinks JavaScript dependency footprint in pnpm projects and cleans up lockfiles while preserving workspace layouts. Best for trimming node_modules in Grafana plugins. CX Codex +1 3,200installs dependencies-audit cognitedata The dependencies-audit skill finds vulnerabilities, outdated and deprecated packages, license problems and supply-chain risks, then fixes them instead of only reporting. CX Codex +1 1,900installs om-auto-audit-dependencies open-mercato om-auto-audit-dependencies — a skill for Claude Code that scans project lockfiles for security advisories using native audit tools or the OSV database. Files deduplicated tracker issues with minimal upgrade targets. CX Codex +1 614installs remove-unused-dependencies Legion Code Inc. remove-unused-dependencies audits selected dependencies inside an approved package and lockfile scope, then checks imports, tests, builds, and packaging before removal. CX Codex +1 ★ 96repo stars uv-advanced-dependencies laurigates uv-advanced-dependencies is a skill for managing non-standard dependency sources in uv, including GitHub repositories, editable local packages, and private indexes. It covers projects that need Git, local path, or custom index dependencies. CX Codex +1 332installs code-architecture-review omer-metin code-architecture-review evaluates codebase structure for module dependencies and coupling. Catches architectural problems before they turn into debt. CX Codex +1 270installs

From the same set112

The whole set →
test-engineer test-engineer writes unit, integration and end-to-end tests for the code you just finished, then reports coverage by line, branch and function. Useful when a feature works but nothing guards it. CX Codex ★ 1,357repo stars audit-layer-boundaries audit-layer-boundaries analyzes architectural layer boundaries in Rust projects. It catches mixed responsibilities, misplaced database logic, and boundary leaks. CX Codex +1 ★ 1,357repo stars skill-generator-agent skill-generator-agent turns a skill spec into files on disk: SKILL.md, helper scripts, reference docs. Then it checks frontmatter and layout. CX Codex ★ 1,357repo stars milestone-tracker milestone-tracker aggregates milestone data from Linear, GitHub, and git history to calculate burn-down velocity and spot schedule risks. CX Codex +1 ★ 1,357repo stars build-skill build-skill walks a new Claude skill through four agents: requirement questions, file generation, validation, docs. You approve the spec before any file appears. CX Codex +1 ★ 1,357repo stars spec-elicitation spec-elicitation conducts a rigorous interview to turn rough feature concepts into detailed technical specifications before writing code. CX Codex +1 ★ 1,357repo stars audit-ports-adapters The audit-ports-adapters command audits ports and adapters in Rust code, checking trait placement, implementations, and whether use cases depend on abstractions. CX Codex +1 ★ 1,357repo stars project-architect project-architect analyzes project requirements, recommends a tech stack, and scaffolds folder structure for new projects or architecture refactoring. Handles web apps, microservices, monorepos, and backend services. CX Codex ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open