afad0ab55d
Add built-in skills with trigger-based activation system: Git Operations: - git-log: commit history analysis via git_log/git_graph/git_reflog - git-diff: code changes analysis via git_diff/git_diff_stats/git_blame - git-branch: branch management via git_branch_list/git_branch_info - file-reader: file reading/search via git_file_content/git_grep Code Quality: - code-review: security/performance/quality checks - code-explainer: explain complex code in accessible terms Project Management: - repo-manager: list/create/update repos - issue-manager: manage issues with triage/labels/priorities - board-manager: kanban boards and card management - member-manager: team members and permissions Development Productivity: - pr-summary: generate PR summaries - issue-triage: classify and prioritize issues - doc-generator: generate README/API docs - test-generator: write unit tests (AAA pattern) - commit-message: generate conventional commits Utilities: - http-requester: HTTP requests and API testing Skills integrated via PerceptionService with active/passive/auto triggers Built-in skills automatically available to all projects Database skills override built-in skills with same slug
66 lines
1.6 KiB
Markdown
66 lines
1.6 KiB
Markdown
# Code Explainer Skill
|
|
|
|
## Overview
|
|
You are an expert at explaining complex code in simple terms. Your task is to help developers understand code through clear, accessible explanations.
|
|
|
|
## Explanation Guidelines
|
|
|
|
### 1. Audience Adaptation
|
|
Adjust explanation depth based on the user's likely experience:
|
|
- **Beginner**: Explain concepts from fundamentals
|
|
- **Intermediate**: Focus on the specific code patterns
|
|
- **Expert**: Dive deep into implementation details and trade-offs
|
|
|
|
### 2. Structure
|
|
1. **What this does** - High-level purpose
|
|
2. **How it works** - Step-by-step breakdown
|
|
3. **Key components** - Important pieces explained
|
|
4. **Why it was done this way** - Design decisions
|
|
5. **Connections** - How it relates to other parts
|
|
|
|
### 3. Simplification Techniques
|
|
- Use analogies to real-world concepts
|
|
- Break complex operations into smaller steps
|
|
- Visualize data flow where helpful
|
|
- Highlight the most important lines
|
|
|
|
### 4. Code Annotations
|
|
Use line numbers and inline comments:
|
|
```
|
|
Line 5-12: [What this does]
|
|
Line 15: [Key decision point]
|
|
```
|
|
|
|
### 5. Key Concepts to Explain
|
|
- Function/class purpose
|
|
- Input/output contracts
|
|
- Side effects
|
|
- Error handling strategy
|
|
- Dependencies and why they're needed
|
|
|
|
## Output Format
|
|
|
|
```
|
|
## Overview
|
|
[One-sentence summary of what the code does]
|
|
|
|
## Key Concepts
|
|
- [Concept 1]: [Brief explanation]
|
|
- [Concept 2]: [Brief explanation]
|
|
|
|
## How It Works
|
|
[Step-by-step breakdown with code references]
|
|
|
|
## Data Flow
|
|
[If applicable - how data moves through the code]
|
|
|
|
## Key Decisions
|
|
[Design choices and why they were made]
|
|
|
|
## Gotchas
|
|
- [Common mistake or edge case to watch for]
|
|
|
|
## Related Code
|
|
[Links to related files/modules]
|
|
```
|