architectural-analysis
"Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior
npx skills add testdouble/han --skill architectural-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase.
How it works
Assembles a roster of agents to inspect the focus area. It validates the focus area resolves to real files using Glob and Read, classifies size starting at small, and dispatches a fixed synthesis spine: han-core:structural-analyst, han-core:behavioral-analyst, han-core:risk-analyst, and han-core:software-architect. Depending on signals (concurrency, security, data, DevOps, system seam, unfamiliar area), it may add signalled specialists (e.g., han-core:concurrency-analyst, SEC-###, han-core:data-engineer, han-core:devops-engineer, han-core:on-call-engineer, han-core:codebase-explorer, han-core:system-architect) when the band allows. The skill never modifies code and writes a synthesized report grounded in the findings.
When to use it
Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review.
What it can touch
The skill relies on Glob and Read to resolve the focus area to real files. It may dispatch agents that inspect structure, data flow, and risk within those files, but it does not itself modify code.
Caveats
The skill is constrained to architectural analysis of a defined focus area and does not produce refactor proposals itself; recommendations related to boundaries may be synthesized by downstream agents. No outcomes are promised beyond the analysis and reporting produced by the dispatched specialists.
## Project Context - git installed: !`which git 2>/dev/null || echo "not installed"` - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` - personal config directory: !`echo "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. ## Operating Principles Read these before dispatching anything. They constrain every step below. - **A focus area is required.** This skill analyzes a specific module, directory, or feature. "Analyze the whole codebase" is not a valid input. If no focus area resolves to real files, stop and ask the user to name one. - **The agents own the judgment; the skill orchestra
- Project Context
- Operating Principles
- Step 1: Validate the Focus Area and Resolve Project Context
- Step 2: Detect Signals and Classify Size
- Step 3: Build the Roster and Announce It
- Step 4: Dispatch the Discovery Wave in Parallel
- Step 5: Compile the Discovery Findings
- Step 6: Dispatch the Risk Analyst
- Step 7: Dispatch the Synthesis Architects
- Step 8: Render the Report
- Step 9: Rewrite the Report for Readability
- Step 10: Run the Readability Self-Check
- Step 11: Present the Report
What does the architectural-analysis skill do?
"Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior
How do I install it?
Run `npx skills add testdouble/han --skill architectural-analysis --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 testdouble/han, a repository with 154 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.