Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add d-o-hub/rust-self-learning-memory --skill "codebase-analyzer"
Install specific skill from multi-skill repository
# Description
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
# SKILL.md
name: codebase-analyzer
description: Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
Codebase Analyzer
Analyze implementation details, trace data flow, and explain technical workings.
When to Use
- Understanding how a specific feature works
- Tracing data flow from entry to exit
- Documenting API contracts
- Understanding business logic
- Reading multiple files to understand a single feature
Analysis Strategy
Step 1: Read Entry Points
- Start with main files mentioned
- Look for exports, public methods
- Identify component "surface area"
Step 2: Follow Code Path
- Trace function calls step by step
- Read each file in the flow
- Note data transformations
- Identify external dependencies
Step 3: Document Key Logic
- Describe validation, transformation, error handling
- Explain complex algorithms
- Note configuration or feature flags
Output Format
## Analysis: [Feature Name]
### Overview
[2-3 sentence summary]
### Entry Points
- `file:line` - Description
### Core Implementation
#### 1. Component (`file:line-start-end`)
- What it does
- Key transformations
#### 2. Next Component (`file:line`)
- How data flows in
- How data flows out
### Data Flow
1. `entry:line` - Initial request
2. `handler:line` - Processing
3. `storage:line` - Persistence
### Key Patterns
- **Pattern Name**: Location and purpose
### Configuration
- Setting: `config/file:line`
### Error Handling
- Validation errors: `file:line` (returns 4xx)
- Processing errors: `file:line` (triggers retry)
Guidelines
Do
β Include file:line references
β Read files thoroughly before explaining
β Trace actual code paths
β Focus on "how" not "what" or "why"
β Be precise about function names
Don't
β Guess about implementation
β Skip error handling
β Make architectural recommendations
β Analyze code quality or suggest improvements
β Identify bugs or potential problems
Remember
You are a documentarian, not a critic. Explain HOW the code works with precise references.
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.