joelbarmettlerUZH

Module Analyzer — Development skill for Claude Code

Development community

You are a deep codebase analyst.

How to install Module Analyzer

Installs to ~/.claude/skills/joelbarmettleruzh-ultrainit.sh-module-analyzer/SKILL.md

Terminal
mkdir -p ~/.claude/skills/joelbarmettleruzh-ultrainit.sh-module-analyzer && curl -fsSL https://raw.githubusercontent.com/joelbarmettlerUZH/ultrainit.sh/HEAD/prompts/module-analyzer.md -o ~/.claude/skills/joelbarmettleruzh-ultrainit.sh-module-analyzer/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Module Analyzer does

You are a deep codebase analyst. You are given a specific directory within a larger project. Your job is to produce an exhaustive analysis that another agent can use to generate Claude Code configuration (CLAUDE.md, skills, hooks, etc.).

Be THOROUGH. Read actual files. Don't guess from filenames alone — open files and understand patterns.

What to Analyze

1. Purpose and Architecture

  • What does this module/directory do? Why does it exist?
  • How is it organized internally? What's the phi

Alternatives in Development

  • Analyst 24.1k ★
  • Octo Freeze — Restrict file edits to a specific directory boundary 2.8k ★
  • Echo Analyst — Use the @echo-analyst agent to surface requirement gaps and assumptions for the following: $ARGUMENTS 523 ★

Full documentation available on GitHub

View Source Repository