Skip to main content
skill CX Codex

architectural-analysis — Claude Code skill: what it does

Audits a codebase for design problems: dead exports, duplicated duties, tangled types, dependency cycles. Read-only unless you've already allowed fixes.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pedronauck/skills --skill architectural-analysis -a claude-code
Open on GitHub

What architectural-analysis does

The skill works inside the scope you give it. It first maps entry points and dependencies with rg --files and targeted searches, then sorts candidates against the signal catalog in references/detection-catalog.md. Treat the thresholds there as hints, not verdicts.

Nothing gets called dead until dynamic imports, reflection, framework hooks, tests and published APIs have been checked. A public export with no consumer in this checkout stays. Every serious finding is tied to source: path, line, the maintenance cost it causes, and the smallest change worth making.

Broad audits follow assets/report-template.md and land in .audits/architectural-analysis-<timestamp>.md, with inspected and uninspected areas kept apart. Formatting, performance profiling, security work and feature-level review sit outside this scope. On its own the audit changes nothing in your project; applying findings needs authorization you gave up front.

What it helps with

  • locate dead exports and responsibilities that overlap
  • untangle dependency cycles between modules
  • spot where type ownership has gone wrong
  • get a report citing paths and lines instead of vague complaints

Example prompts for the agent

  • Run an architecture audit on the billing package and point out the overlapping responsibilities
  • Write the audit report into .audits and say which areas you skipped
  • Check whether the export in src/legacy/index.ts is used anywhere

How to install architectural-analysis

1Skills CLI (Vercel)

npx skills add pedronauck/skills --skill architectural-analysis -a claude-code

2Manually: put the files in place

~/.claude/skills/architectural-analysis/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/architectural-analysis/

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

Questions about architectural-analysis

How do I install architectural-analysis in Claude Code?

Run npx skills add pedronauck/skills --skill architectural-analysis -a claude-code. The skill ends up in ~/.claude/skills/architectural-analysis/SKILL.md.

What does architectural-analysis do?

It audits design: dead code, duplication, type confusion and costly change patterns. Findings are verified in source, each with a minimal suggested fix.

Does it delete dead code on its own?

An audit only reads. Remediation happens if explicit authorization already exists.

Similar skills

All skills for Code review and refactoring →

From the same set18

no-workarounds This skill examines fixes that conceal an error or its symptoms. Use it when a change looks like a workaround or the defect comes from outside your codebase. CX Codex +1 566installs typescript-advanced Guides agents through advanced TypeScript types and compile-time contracts. Use it when generic inference or reusable type utilities are the hard part. CX Codex +1 552installs qa-report This skill maintains project QA docs, maps user journeys, and plans persona-led sessions. Use it to keep planning and bug records connected across QA cycles. CX Codex +1 525installs react Guidance for building and reviewing React 19 components and hooks with React Compiler in mind. Use it for compiler setup, state and Effects decisions, or component tests. CX Codex +1 448installs tailwindcss Guides coding agents through Tailwind CSS v4 component styling using project tokens, explicit utility classes, and accessible layouts. CX Codex +1 447installs refactoring-analysis Audits architectural health and Fowler code smells, writing prioritized refactoring plans to docs/_refacs/. Built for planning refactoring while preserving existing behavior. CX Codex +1 404installs electron-builder Guides the agent through configuring Electron app packaging, platform targets, code signing, and auto-updates. Useful for release workflows. CX Codex +1 392installs next-best-practices A skill that hands your agent a set of Next.js rules: file conventions, RSC boundaries, async APIs, metadata, error handling. Useful whenever it writes or reviews Next.js code. CX Codex +1 383installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor