Analyze coding growth and patterns
developer-growth-analysisskillsetup L2★412
ECNU-ICALK/AutoSkill ↗Causal-lift measurements
code-audit-4pp vs no-skill baselinewith-skill 43% · baseline 46%
Measured by running the task with and without this artifact, K=5, graded by deterministic checks — no LLM judging.
What it does
Analyze recent coding work patterns and gaps
Best for
Developers who want structured, evidence-based feedback on their work growth without waiting for code reviews, using their actual recent project history as the signal.
Inputs
- · Your Claude Code chat history from past 24-48 hours
Outputs
- · Personalized growth report with improvement areas
- · Curated HackerNews reading list tailored to skill gaps
- · Slack DM delivery of complete report
Requires
- · Claude Code chat history (JSONL format at ~/.claude/history.jsonl)
- · HackerNews API/access for article curation
- · Slack API for DM delivery
Preconditions
- · Claude Code enabled and running with history logging active
- · Slack account authenticated and DMs accessible
Failure modes
- · Depends on chat history being complete and formatted correctly
- · Only analyzes what appears in chats; debugging done silently in IDE not captured
- · HackerNews curation may miss newly-published content relevant to cutting-edge skills
- · Assumes improvement areas can be identified from chat patterns; works best with varied project work
Trust signals
- · Six-step methodology: read history → identify patterns → detect gaps → generate report → find learning resources → deliver to Slack
- · Analyzes specific dimensions: project domains, technologies, problem types, challenges, approach patterns
- · Reads from JSONL format with fields (display, project, timestamp, pastedContents)
- · Filters for time window (24-48 hours) and aggregates patterns
- · Integrates curated learning resources from HackerNews directly matching identified gaps