Developer Growth Analysis
Turn recent Claude Code sessions into a personal skill-gap report with HackerNews reading list and a Slack DM summary.
Overview
Developer Growth Analysis is an agent skill most often used in Grow (also Operate) that analyzes recent Claude Code chat history, identifies coding patterns and gaps, curates HackerNews resources, and can deliver a perso
Install
npx skills add https://github.com/composiohq/awesome-claude-skills --skill developer-growth-analysisWhat is this skill?
- Six-step pipeline: ingest chat history, pattern detection, gap mapping, resource curation, synthesis, Slack delivery
- Uses local Claude Code chat history from roughly the last 24–48 hours as the evidence base
- Surfaces recurring technologies, problem types, and friction themes without waiting on human code review
- Curates HackerNews articles matched to identified gaps and improvement areas
- Delivers a personalized growth report to your Slack DMs when configured
- Six-step analysis pipeline described in the skill documentation
- Chat history window of approximately the past 24–48 hours
Adoption & trust: 2.3k installs on skills.sh; 63.7k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You ship constantly with your coding agent but only get feedback on individual tasks, so you cannot see recurring gaps or what to learn next from your own work history.
Who is it for?
Solo builders using Claude Code daily who want periodic, history-based skill feedback and a short reading list without formal mentorship.
Skip if: Teams needing org-wide engineering metrics, HR performance reviews, or security/compliance audits of code quality—this reads chat transcripts for personal growth, not production SLOs.
When should I use this skill?
You want to understand development patterns from recent work, identify technical gaps, get curated HackerNews learning resources tailored to those patterns, or receive a personalized growth report in Slack without waitin
What do I get? / Deliverables
You receive a data-backed picture of recent patterns, prioritized improvement areas, and curated articles—optionally in Slack—so you can iterate how you build before the next sprint of features.
- Personalized developer growth report (patterns, gaps, improvement areas)
- Curated HackerNews article list matched to identified gaps
- Optional Slack DM summary of the report
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because the output compounds how you work over time—patterns, gaps, and learning—not a one-off build or ship task. Analytics fits best: it quantifies habits and recurring challenges from chat history the way product analytics quantifies user behavior, but aimed at developer capability.
Where it fits
After a week of feature work, run the skill to see which APIs and debugging loops dominated your chats and which topics deserve deeper study.
Between releases, use the report to adjust how you prompt and structure tasks so the same mistakes do not repeat across sessions.
When adopting a new stack with your agent, compare early-session confusion themes in the analysis to confirm you are learning the right primitives first.
Following a crunch of fixes, scan the growth summary for recurring review themes you could turn into a checklist skill for the next ship cycle.
How it compares
Use for longitudinal habit insights from agent chats instead of a one-shot PR code-review skill on a single change.
Common Questions / FAQ
Who is developer-growth-analysis for?
It is for solo and indie developers who rely on Claude Code and want personalized growth feedback derived from their own recent sessions, plus optional Slack delivery and HackerNews links.
When should I use developer-growth-analysis?
Use it in Grow when you want to compound skills after a busy coding week; in Operate when you want to iterate your agent workflow habits; and anytime you want gap analysis and curated reading without waiting for a human review cycle.
Is developer-growth-analysis safe to install?
It needs access to local chat history and may call external services (HackerNews, Slack); review the Security Audits panel on this Prism page and your token scopes before enabling Slack or automated sends.
SKILL.md
READMESKILL.md - Developer Growth Analysis
# Developer Growth Analysis 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. ## When to Use This Skill Use this skill when you want to: - Understand your development patterns and habits from recent work - Identify specific technical gaps or recurring challenges - Discover which topics would benefit from deeper study - Get curated learning resources tailored to your actual work patterns - Track improvement areas across your recent projects - Find high-quality articles that directly address the skills you're developing 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. ## What This Skill Does This skill performs a six-step analysis of your development work: 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. 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. 3. **Detects Improvement Areas**: Recognizes patterns that suggest skill gaps, repeated struggles, inefficient approaches, or areas where you might benefit from deeper knowledge. 4. **Generates a Personalized Report**: Creates a comprehensive report showing your work summary, identified improvement areas, and specific recommendations for growth. 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. 6. **Sends to Your Slack DMs**: Automatically delivers the complete report to your own Slack direct messages so you can reference it anytime, anywhere. ## How to Use Ask Claude to analyze your recent coding work: ``` Analyze my developer growth from my recent chats ``` Or be more specific about which time period: ``` Analyze my work from today and suggest areas for improvement ``` The skill will generate a formatted report with: - Overview of your recent work - Key improvement areas identified - Specific recommendations for each area - Curated learning resources from HackerNews - Action items you can focus on ## Instructions When a user requests analysis of their developer growth or coding patterns from recent work: 1. **Access Chat History** Read the chat history from `~/.claude/history.jsonl`. This file is a JSONL format where each line contains: - `display`: The user's message/request - `project`: The project being worked on - `timestamp`: Unix timestamp (in milliseconds) - `pastedContents`: Any code or content pasted Filter for entries from the past 24-48 hours based on the current timestamp. 2. **Analyze Work Patterns** Extract and analyze the following from the filtered chats: - **Projects and Domains**: What types of projects was the user working on? (e.g., backend, frontend, DevOps, data, etc.) - **Technologies Used**: What languages, frameworks, and tools appear in the conversations? - **Problem Types**: What categories of problems are being solved? (e.g., performance optimization, debugging, feature implementation, refactoring, setup/configuration) - **Challenges Encountered**: What problems did the user struggle with? Look for: - Repeated questions about similar topics - Problems that took multiple attempts to solve - Questions indicating knowledge gaps