developer-growth-analysis

Developer Growth Analysis

Skill Overview

Developer Growth Analysis analyzes your Claude Code chat history to identify coding patterns, skill gaps, and areas for improvement. It curates relevant learning resources from Hacker News and automatically sends personalized growth reports to your Slack direct messages.

Use Cases

1. Regular Self-Assessment of Your Skills

When you want to understand your development habits and programming patterns, this skill can analyze your chat history from the past 24–48 hours to identify the technologies you use, the types of problems you solve, the challenges you encounter, and your approaches to solving them. Through regular developer growth analyses, you can track your skill development over time and discover areas that need strengthening.

2. Discovering Technical Weaknesses

If you repeatedly encounter similar problems at work, or often need multiple attempts to solve issues in a particular technical area, this skill can help you identify these patterns. For example, it may discover knowledge gaps in areas such as TypeScript type safety, error handling, asynchronous programming patterns, or database query optimization, and provide specific recommendations for improvement.

3. Getting Personalized Learning Resources

Unlike generic programming tutorial recommendations, this skill searches Hacker News and curates high-quality articles and discussions directly related to the areas for improvement identified from your actual work patterns. Whether you want to learn advanced TypeScript patterns, secure data handling on the frontend, or React component architecture, you will receive a reading list tailored to the needs of your current project.

Core Features

1. Chat History Analysis and Pattern Recognition

This skill reads your ~/.claude/history.jsonl file, filters conversation records from the past 24–48 hours, and analyzes your projects and domains (backend, frontend, DevOps, etc.), the technology stack you use, the types of problems you encounter (performance optimization, debugging, feature implementation, etc.), the challenges you face, and your problem-solving approaches. Through this analysis, it can identify patterns that indicate skill gaps, repeated struggles, or inefficient methods.

2. Personalized Growth Report Generation

Based on the analysis results, the skill generates a comprehensive developer growth report that includes a work summary, 3–5 prioritized areas for improvement, observed strengths, and specific learning action items. For each area, it explains “Why It Matters,” “What I Observed,” “Recommended Improvements,” and an estimated “Time to Improve the Skill.” The report ensures that every recommendation is supported by evidence from your actual chat history rather than vague feedback.

3. Intelligent Learning Resource Curation and Delivery

Using Rube MCP to search Hacker News, the skill finds 2–3 highly relevant, high-engagement articles for each identified area for improvement, including the article title, publication date, a description of its relevance, and a link. The final report is automatically sent to your Slack direct messages and organized into several logically structured sections (summary, areas for improvement, strengths, action items, and resources), allowing you to reference it whenever needed and focus on improvement over the following week.

Frequently Asked Questions

How does Developer Growth Analysis analyze my chat history?

This skill reads your local ~/.claude/history.jsonl file, a JSONL-formatted file in which each line contains your user messages, project information, timestamps, and pasted content. It filters records from the past 24–48 hours and analyzes the languages and frameworks you use, the types of problems you solve, the challenges you encounter, and your problem-solving approaches. All analysis is performed locally and is based on your actual coding patterns, ensuring that the recommendations are relevant and accurate.

What kinds of programming problems can this skill help me identify?

The skill identifies specific, actionable areas for improvement rather than vague suggestions such as “improve your coding skills.” For example, it might discover that you “struggle with TypeScript type safety, particularly when handling union types for connection configurations,” or that “you patched several errors related to null checks, indicating a need to strengthen error handling and validation.” Every issue is based on evidence from your actual chat history and includes specific recommendations for improvement and time estimates.

How is this skill different from a traditional code review?

Traditional code reviews rely on others providing feedback on your code, require waiting for reviewers’ time, and often focus on a single pull request or specific feature. Developer Growth Analysis, by contrast, evaluates your overall work patterns, provides immediate feedback, covers a broader range of skills (including technology choices, problem-solving approaches, and learning curves), and offers personalized learning resources. It does not replace code reviews; it complements them by helping you continue improving even when external feedback is unavailable.