developer-growth-analysis_skill

Overview

This skill analyzes your recent Claude Code chat history to surface coding patterns, recurring challenges, and targeted areas for improvement. It curates high-quality HackerNews learning resources relevant to those gaps and delivers a personalized growth report directly to your Slack DMs. The report is actionable and prioritized so you can focus on the highest-impact improvements first.

How this skill works

The skill reads your local Claude Code history from the past 24–48 hours, extracting project context, pasted code, and timestamps to build an evidence-backed profile of recent work. It classifies project types, technologies, problem categories, and approach patterns, then identifies 3–5 prioritized improvement areas with concrete recommendations. For each area it searches HackerNews for high-engagement articles and packages the findings into a readable report, which is automatically sent to your Slack direct messages.

When to use it

• After a focused coding session to get a quick assessment of your strengths and gaps
• When you notice repeated bugs or pattern-based problems and want evidence-based guidance
• Before planning a learning sprint so you can prioritize topics tied to real work
• To prepare a concise growth update to share with a mentor or manager
• When you want curated HackerNews resources that match your actual development needs

Best practices

• Run the analysis soon after work (within 24–48 hours) so findings reflect recent context
• Allow the tool to access only the relevant local Claude history file and review the extracted entries
• Treat the recommendations as prioritized experiments: pick one action item for this week
• Use the curated articles as study prompts and apply learnings to the concrete code snippets flagged in the report
• Re-run periodically to track improvement and validate whether recurring issues persist

Example use cases

• You completed several TypeScript tasks and want focused guidance on advanced typing patterns to reduce runtime bugs
• You wrestled with async timing issues across services and need prioritized steps to eliminate race conditions
• You fixed a UI data-leak and want curated resources plus a checklist to prevent similar leaks in future
• You’re preparing a one-week learning plan tied to the exact problems you encountered yesterday
• You want a concise report in Slack to share with a mentor before a 1:1