developer-growth-analysis

Analyze Claude Code chat history to identify coding patterns and learning gaps.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dr-code/beacon --skill developer-growth-analysis-dr-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-growth-analysis
Source: https://github.com/dr-code/beacon/tree/main/plugins/all-skills/skills/developer-growth-analysis
Command: npx skills add https://github.com/dr-code/beacon --skill developer-growth-analysis-dr-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often lack structured, evidence-based feedback derived from their own recent work, making it hard to prioritize learning or address recurring technical gaps. This Skill analyzes your recent Claude Code chat interactions to reveal patterns, recurring challenges, and specific areas that will most improve your development velocity.

Core Features & Use Cases

  • Chat history analysis: Reads local Claude Code history to extract projects, technologies, problem types, and timestamps to form an evidence-backed view of recent work.
  • Improvement detection: Identifies 3–5 prioritized, actionable improvement areas grounded in actual chat evidence and typical developer workflows.
  • Curated learning resources: Searches HackerNews for high-quality articles and discussions relevant to the identified gaps and includes concise explanations and links.
  • Delivery to Slack: Sends a formatted, shareable developer growth report directly to the user's Slack DMs for easy review and tracking.

Quick Start

Analyze my developer growth from my recent Claude Code chats and send a prioritized growth report with curated HackerNews resources to my Slack DMs.

Frequently Asked Questions about developer-growth-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze my Claude Code chat history to find coding patterns and learning gaps?

Yes, you can generate personalized developer growth reports by analyzing recent Claude Code sessions. This process extracts problem types and timestamps from your chat history to identify 3 to 5 prioritized, actionable improvement areas grounded in your actual coding evidence.

Does sending a developer growth report to Slack require local history access?

Yes, sending a developer growth report to Slack requires local access to your ~/.claude/history.jsonl file. The Skill reads this chat history to extract coding patterns and then uses an authenticated Slack connection to deliver the formatted analysis directly to your DMs.

How do I find curated HackerNews learning resources for my specific coding gaps?

Finding curated HackerNews learning resources for coding gaps requires searching for high-quality articles relevant to your identified technical deficiencies. This Skill uses Rube MCP-enabled search to find discussions and includes concise explanations and links tailored to your improvement areas.

What is the time range for Claude Code chat history analysis when generating growth reports?

The time range for Claude Code chat history analysis covers your past 24 to 48 hours of recent sessions. This timeframe ensures the extracted projects, technologies, and problem types reflect your most current development patterns and immediate technical challenges.

Can I use Claude Code history analysis without an authenticated Slack connection?

No, an authenticated Slack connection is required to deliver the formatted developer growth report. While the local history analysis identifies your coding gaps and curated resources, the final formatted report relies on Slack DMs for easy review and tracking.