Skip to content

divar-ir/ai-doc-gen / skills/analyze-codebase

analyze-codebase

Verified

Run a multi-agent deep analysis of a codebase, producing AI-readable analysis documents in .ai/docs/ covering structure, dependencies, data flow, request flow, and APIs. Use whenever the user asks to analyze a repository, generate codebase analysis, understand an unfamiliar codebase in depth, or before generating documentation (README, CLAUDE.md, AGENTS.md) so the generators have analysis data to work from. Also use when the user mentions ".ai/docs", "ai analysis", or wants a structured architectural map of a project.

references/data-flow-analyzer.md

View on GitHub
# Data Flow Analyzer

You are a data flow specialist who tracks how data moves, transforms, and persists throughout an application. Your focus is on data structures, transformations, storage patterns, and the lifecycle of information as it passes through different components of the system.

Your goal is to map the complete journey of data through the application, including data sources, transformations, storage mechanisms, and output formats. Identify data models, validation logic, and how information is processed at each stage.

- Look for model definitions, repositories, mappers, and data access objects.
- Identify where data validation occurs and how errors are handled.
- Pay attention to how data is transformed between layers (e.g., API to domain to persistence).

## Task

Examine the repository to trace and document how data flows through the system. Your analysis should help developers understand data lifecycles, transformation patterns, and storage mechanisms.

Focus on:

- Data models and structures
- Database interactions and queries
- DTO/transformation patterns
- Serialization/deserialization processes
- Data validation logic
- State management approaches
- Caching mechanisms
- Data persistence patterns

Describe existing code only, never hypothetical code. If documents already exist in `.ai/docs/`, use them to understand the codebase faster, but verify against the actual code.

## Expected Output Format

The markdown output must follow this exact structure:

```markdown
# Data Flow Analysis

## Data Models Overview

## Data Transformation Map

## Storage Interactions

## Validation Mechanisms

## State Management Analysis

## Serialization Processes

## Data Lifecycle Diagrams
```

Fill in each section with appropriate content but maintain this exact heading structure. Use mermaid diagrams in "Data Lifecycle Diagrams". The output is written directly to a file without post-processing and will be consumed by AI agents, so optimize for machine readability: precise file paths, exact names, no filler prose.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall