Agent skill · Security

architecture-audit

Perform comprehensive software architecture audits to identify improvements for robustness, changeability, and testability. Use when asked to audit, review, or analyze a codebase's architecture, or when asked to suggest structural improvements. Triggers include "architecture audit", "audit the codebase", "review architecture", "architectural analysis", "code structure review", or explicit "/architecture-audit".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill architecture-audit --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/architecture-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

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

From the SKILL.md

# Architecture Audit Analyze a codebase's architecture and provide actionable recommendations to improve robustness, changeability, and testability. ## Audit Process 1. **Understand scope** - Identify target directories/modules 2. **Map structure** - Explore directory layout and key files 3. **Analyze each dimension** - Work through checklist systematically 4. **Synthesize findings** - Identify patterns and root causes 5. **Generate report** - Deliver prioritized recommendations ## Step 1: Scope & Context Determine audit scope: - Full codebase or specific modules? - Any known pain points to focus on? - Primary language(s) and frameworks? Use Glob and Grep to understand: ``` # Directory structure ls -la, tree (if available) # Key configuration files package.json, requirements.txt, go.mod, Cargo.toml, etc. # Entry points main.*, index.*, app.* ``` ## Step 2: Structure Mapping Build mental model of the codebase: - Identify top-level organization (by feature, layer, or domain?) - Map module boundaries and dependencies - Note test location and structure - Identify configuration management approach ## Step 3: Systematic Analysis Work through each dimension. Load [references/audit-checkli

What's inside
Steps it walks through
  1. Audit Process
  2. Step 1: Scope & Context
  3. Step 2: Structure Mapping
  4. Step 3: Systematic Analysis
  5. Step 4: Synthesis
  6. Step 5: Report Generation
  7. Key Principles
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the architecture-audit skill do?

Perform comprehensive software architecture audits to identify improvements for robustness, changeability, and testability. Use when asked to audit, review, or analyze a codebase's architecture, or when asked to suggest structural improvements. Triggers include "architecture audit", "audit the codebase", "review architecture", "architectural analysis", "code structure review", or explicit "/architecture-audit".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill architecture-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 majiayu000/claude-skill-registry, a repository with 534 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