developer-growth-analysis

Name: developer-growth-analysis
Author: ECNU-ICALK

524stars49forks

How to install developer-growth-analysis?

ecnu-icalk/autoskill/developer-growth-analysis

$npx -y skills add ECNU-ICALK/AutoSkill --skill developer-growth-analysis

Installs into the current project.

Summary

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

Files · 1

View on GitHub

SKILL.md

1	# Developer Growth Analysis
2
3	This skill provides personalized feedback on your recent coding work by analyzing your Claude Code chat interactions and identifying patterns that reveal strengths and areas for growth.
4
5	## When to Use This Skill
6
7	Use this skill when you want to:
8	- Understand your development patterns and habits from recent work
9	- Identify specific technical gaps or recurring challenges
10	- Discover which topics would benefit from deeper study
11	- Get curated learning resources tailored to your actual work patterns
12	- Track improvement areas across your recent projects
13	- Find high-quality articles that directly address the skills you're developing
14
15	This skill is ideal for developers who want structured feedback on their growth without waiting for code reviews, and who prefer data-driven insights from their own work history.
16
17	## What This Skill Does
18
19	This skill performs a six-step analysis of your development work:
20
21	1. Reads Your Chat History: Accesses your local Claude Code chat history from the past 24-48 hours to understand what you've been working on.
22
23	2. Identifies Development Patterns: Analyzes the types of problems you're solving, technologies you're using, challenges you encounter, and how you approach different kinds of tasks.
24
25	3. Detects Improvement Areas: Recognizes patterns that suggest skill gaps, repeated struggles, inefficient approaches, or areas where you might benefit from deeper knowledge.
26
27	4. Generates a Personalized Report: Creates a comprehensive report showing your work summary, identified improvement areas, and specific recommendations for growth.
28
29	5. Finds Learning Resources: Uses HackerNews to curate high-quality articles and discussions directly relevant to your improvement areas, providing you with a reading list tailored to your actual development work.
30
31	6. Sends to Your Slack DMs: Automatically delivers the complete report to your own Slack direct messages so you can reference it anytime, anywhere.
32
33	## How to Use
34
35	Ask Claude to analyze your recent coding work:
36
37	```
38	Analyze my developer growth from my recent chats
39	```
40
41	Or be more specific about which time period:
42
43	```
44	Analyze my work from today and suggest areas for improvement
45	```
46
47	The skill will generate a formatted report with:
48	- Overview of your recent work
49	- Key improvement areas identified
50	- Specific recommendations for each area
51	- Curated learning resources from HackerNews
52	- Action items you can focus on
53
54	## Instructions
55
56	When a user requests analysis of their developer growth or coding patterns from recent work:
57
58	1. Access Chat History
59
60	Read the chat history from `~/.claude/history.jsonl`. This file is a JSONL format where each line contains:
61	- `display`: The user's message/request
62	- `project`: The project being worked on
63	- `timestamp`: Unix timestamp (in milliseconds)
64	- `pastedContents`: Any code or content pasted
65
66	Filter for entries from the past 24-48 hours based on the current timestamp.
67
68	2. Analyze Work Patterns
69
70	Extract and analyze the following from the filtered chats:
71	- Projects and Domains: What types of projects was the user working on? (e.g., backend, frontend, DevOps, data, etc.)
72	- Technologies Used: What languages, frameworks, and tools appear in the conversations?
73	- Problem Types: What categories of problems are being solved? (e.g., performance optimization, debugging, feature implementation, refactoring, setup/configuration)
74	- Challenges Encountered: What problems did the user struggle with? Look for:
75	- Repeated questions about similar topics
76	- Problems that took multiple attempts to solve
77	- Questions indicating knowledge gaps
78	- Complex architectural decisions
79	- Approach Patterns: How does the user solve problems? (e.g., methodical, exploratory, experimental)
80
81	3. Identify Improvement Areas
82
83	Based on the analysis, identify 3-5 specific areas where the user could improve. These should be:
84	- Specific (not vague like "improve coding skills")
85	- Evidence-based (grounded in actual chat history)
86	- Actionable (practical improvements that can be made)
87	- Prioritized (most impactful first)
88
89	Examples of good improvement areas:
90	- "Advanced TypeScript patterns (generics, utility types, type guards) - you struggled with type safety in [specific project]"
91	- "Error handling and validation - I noticed you patched several bugs related to missing null checks"
92	- "Async/await patterns - your recent work shows some race conditions and timing issues"
93	- "Database query optimization - you rewrote the same query multiple times"
94
95	4. **Gen

People who liked this also viewed

6 picks

Type

developer-growth-analysis

524stars49forks

View on GitHub

How to install developer-growth-analysis?

ecnu-icalk/autoskill/developer-growth-analysis

$npx -y skills add ECNU-ICALK/AutoSkill --skill developer-growth-analysis

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Growth Analysis
2
3	This skill provides personalized feedback on your recent coding work by analyzing your Claude Code chat interactions and identifying patterns that reveal strengths and areas for growth.
4
5	## When to Use This Skill
6
7	Use this skill when you want to:
8	- Understand your development patterns and habits from recent work
9	- Identify specific technical gaps or recurring challenges
10	- Discover which topics would benefit from deeper study
11	- Get curated learning resources tailored to your actual work patterns
12	- Track improvement areas across your recent projects
13	- Find high-quality articles that directly address the skills you're developing
14
15	This skill is ideal for developers who want structured feedback on their growth without waiting for code reviews, and who prefer data-driven insights from their own work history.
16
17	## What This Skill Does
18
19	This skill performs a six-step analysis of your development work:
20
21	1. Reads Your Chat History: Accesses your local Claude Code chat history from the past 24-48 hours to understand what you've been working on.
22
23	2. Identifies Development Patterns: Analyzes the types of problems you're solving, technologies you're using, challenges you encounter, and how you approach different kinds of tasks.
24
25	3. Detects Improvement Areas: Recognizes patterns that suggest skill gaps, repeated struggles, inefficient approaches, or areas where you might benefit from deeper knowledge.
26
27	4. Generates a Personalized Report: Creates a comprehensive report showing your work summary, identified improvement areas, and specific recommendations for growth.
28
29	5. Finds Learning Resources: Uses HackerNews to curate high-quality articles and discussions directly relevant to your improvement areas, providing you with a reading list tailored to your actual development work.
30
31	6. Sends to Your Slack DMs: Automatically delivers the complete report to your own Slack direct messages so you can reference it anytime, anywhere.
32
33	## How to Use
34
35	Ask Claude to analyze your recent coding work:
36
37	```
38	Analyze my developer growth from my recent chats
39	```
40
41	Or be more specific about which time period:
42
43	```
44	Analyze my work from today and suggest areas for improvement
45	```
46
47	The skill will generate a formatted report with:
48	- Overview of your recent work
49	- Key improvement areas identified
50	- Specific recommendations for each area
51	- Curated learning resources from HackerNews
52	- Action items you can focus on
53
54	## Instructions
55
56	When a user requests analysis of their developer growth or coding patterns from recent work:
57
58	1. Access Chat History
59
60	Read the chat history from `~/.claude/history.jsonl`. This file is a JSONL format where each line contains:
61	- `display`: The user's message/request
62	- `project`: The project being worked on
63	- `timestamp`: Unix timestamp (in milliseconds)
64	- `pastedContents`: Any code or content pasted
65
66	Filter for entries from the past 24-48 hours based on the current timestamp.
67
68	2. Analyze Work Patterns
69
70	Extract and analyze the following from the filtered chats:
71	- Projects and Domains: What types of projects was the user working on? (e.g., backend, frontend, DevOps, data, etc.)
72	- Technologies Used: What languages, frameworks, and tools appear in the conversations?
73	- Problem Types: What categories of problems are being solved? (e.g., performance optimization, debugging, feature implementation, refactoring, setup/configuration)
74	- Challenges Encountered: What problems did the user struggle with? Look for:
75	- Repeated questions about similar topics
76	- Problems that took multiple attempts to solve
77	- Questions indicating knowledge gaps
78	- Complex architectural decisions
79	- Approach Patterns: How does the user solve problems? (e.g., methodical, exploratory, experimental)
80
81	3. Identify Improvement Areas
82
83	Based on the analysis, identify 3-5 specific areas where the user could improve. These should be:
84	- Specific (not vague like "improve coding skills")
85	- Evidence-based (grounded in actual chat history)
86	- Actionable (practical improvements that can be made)
87	- Prioritized (most impactful first)
88
89	Examples of good improvement areas:
90	- "Advanced TypeScript patterns (generics, utility types, type guards) - you struggled with type safety in [specific project]"
91	- "Error handling and validation - I noticed you patched several bugs related to missing null checks"
92	- "Async/await patterns - your recent work shows some race conditions and timing issues"
93	- "Database query optimization - you rewrote the same query multiple times"
94
95	4. **Gen

People who liked this also viewed

6 picks

Type