analyze-repo

Analyze Repository

Analyze an existing repository's structure, conventions, and guardrails.

This command runs automatically when /initialize-project detects an existing codebase without Claude setup. You can also run it standalone anytime.

Use this command standalone when:

• You want to re-analyze after making changes
• You want analysis without running /initialize-project
• Auditing code quality and guardrails on any repo
• Reviewing a codebase without adding Claude skills

Automatic trigger:

• /initialize-project on existing codebase → auto-runs this analysis first

---

Phase 1: Repository Detection

Run these checks to understand the repo:

# Git info
echo "=== Git Status ===" && \
git remote -v 2>/dev/null && \
git branch -a 2>/dev/null | head -10 && \
git log --oneline -5 2>/dev/null

# Config files
echo "=== Config Files ===" && \
ls -la *.json *.toml *.yaml *.yml 2>/dev/null

# Directory structure (3 levels, excluding noise)
echo "=== Directory Structure ===" && \
find . -type d -maxdepth 3 \
    -not -path "*/node_modules/*" \
    -not -path "*/.git/*" \
    -not -path "*/venv/*" \
    -not -path "*/__pycache__/*" \
    -not -path "*/dist/*" \
    -not -path "*/build/*" \
    2>/dev/null | head -40

---

Phase 2: Tech Stack Detection

Identify the primary technologies:

# JavaScript/TypeScript
if [ -f "package.json" ]; then
    echo "=== Package.json ===" && \
    cat package.json | head -50
fi

# Python
if [ -f "pyproject.toml" ]; then
    echo "=== pyproject.toml ===" && \
    cat pyproject.toml
fi

# Mobile
ls pubspec.yaml android/build.gradle ios/*.xcodeproj 2>/dev/null

Based on findings, determine:

File	Technology
package.json + tsconfig.json	TypeScript
package.json (no tsconfig)	JavaScript
pyproject.toml	Python
pubspec.yaml	Flutter (Dart)
android/build.gradle	Android Native
Cargo.toml	Rust
go.mod	Go

---

Phase 3: Repo Structure Type