Agent skill · Code Review & Quality

code-analysis

Deep code analysis with metrics, patterns, and recommendations. Use for architecture review, tech debt assessment, codebase exploration, or when asked 'analyze this code/project'.

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill code-analysis-alexandrbasis-wythm-claude-workflo --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Allowed tools: -Read-Grep-Glob-Bash(wc*)-Bash(cloc*)
Path: skills/analysis/code-analysis-alexandrbasis-wythm-claude-workflo/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

# Deep Code Analysis ## Overview Perform comprehensive code analysis returning structured findings. Since this runs in a forked context, explore extensively - only the final report returns to the main conversation. ## Analysis Process ### 1. Scope Discovery ```bash # Understand project structure find . -type f -name "*.ts" | head -50 cloc . --exclude-dir=node_modules,dist,coverage --json 2>/dev/null || wc -l **/*.ts ``` ### 2. Architecture Analysis - Identify layers and boundaries (DDD patterns for Wythm) - Map module dependencies - Find circular dependencies or violations - Check adherence to project patterns (`backend/docs/project-structure.md`) ### 3. Code Quality Metrics - File sizes and complexity hotspots - Test coverage gaps - Code duplication patterns - Naming consistency ### 4. Tech Debt Assessment - TODO/FIXME comments - Deprecated patterns - Missing error handling - Incomplete implementations ### 5. Git History Insights ```bash # Most changed files (churn) git log --format=format: --name-only | grep -v '^$' | sort | uniq -c | sort -rn | head -20 # Recent contributors git shortlog -sn --since="3 months ago" ``` ## Output Format Return a structured report: ```markdown # Co

What's inside
Steps it walks through
  1. Overview
  2. Analysis Process
  3. 1. Scope Discovery
  4. 2. Architecture Analysis
  5. 3. Code Quality Metrics
  6. 4. Tech Debt Assessment
  7. 5. Git History Insights
  8. Output Format
  9. Wythm-Specific Checks
Ships with 1 file
  • metadata.json
Commands it runs
Understand project structure
find . -type f -name "*.ts" | head -50
cloc . --exclude-dir=node_modules,dist,coverage --json 2>/dev/null || wc -l **/*.ts
Most changed files (churn)
git log --format=format: --name-only | grep -v '^$' | sort | uniq -c | sort -rn | head -20
Recent contributors
git shortlog -sn --since="3 months ago"
More from claude-skill-registry
All skills →
About this skill
What does the code-analysis skill do?

Deep code analysis with metrics, patterns, and recommendations. Use for architecture review, tech debt assessment, codebase exploration, or when asked 'analyze this code/project'.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill code-analysis-alexandrbasis-wythm-claude-workflo --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