Back to Details

developer-growth-analysis

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
此Skill通过分析您与Claude Code的聊天交互，针对您近期的编码工作提供个性化反馈，识别能体现您优势与成长空间的模式。

When to Use This Skill

何时使用此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.
当您希望：
  • 从近期工作中了解自己的开发模式与习惯
  • 识别具体的技术短板或反复遇到的挑战
  • 发现哪些主题需要深入学习
  • 获取契合您实际工作模式的定制化学习资源
  • 跟踪近期项目中的可改进领域
  • 找到能直接解决您正在培养的技能相关的高质量文章
此Skill非常适合希望获得结构化成长反馈、无需等待代码评审，且偏好从自身工作历史中获取数据驱动型洞察的开发者。

What This Skill Does

该Skill的功能

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.
此Skill会对您的开发工作执行六步分析：
  1. 读取您的聊天记录：访问您过去24-48小时内的本地Claude Code聊天记录，了解您近期的工作内容。
  2. 识别开发模式：分析您解决的问题类型、使用的技术、遇到的挑战，以及您处理不同任务的方式。
  3. 检测可改进领域：识别表明技能短板、反复出现的困难、低效方法或需要深入学习的领域的模式。
  4. 生成个性化报告：创建一份全面的报告，展示您的工作总结、已识别的可改进领域以及具体的成长建议。
  5. 查找学习资源：利用HackerNews筛选与您的可改进领域直接相关的高质量文章和讨论，为您提供契合实际开发工作的阅读清单。
  6. 发送至Slack私信：自动将完整报告发送至您的Slack私信，方便您随时随地查阅。

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
让Claude分析您近期的编码工作：
Analyze my developer growth from my recent chats
或者更具体地指定时间范围：
Analyze my work from today and suggest areas for improvement
该Skill将生成一份格式规范的报告，包含：
  • 近期工作概述
  • 已识别的关键可改进领域
  • 针对每个领域的具体建议
  • 从HackerNews筛选的学习资源
  • 您可以聚焦的行动项

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
      • Complex architectural decisions
    • Approach Patterns: How does the user solve problems? (e.g., methodical, exploratory, experimental)
  3. Identify Improvement Areas
    Based on the analysis, identify 3-5 specific areas where the user could improve. These should be:
    • Specific (not vague like "improve coding skills")
    • Evidence-based (grounded in actual chat history)
    • Actionable (practical improvements that can be made)
    • Prioritized (most impactful first)
    Examples of good improvement areas:
    • "Advanced TypeScript patterns (generics, utility types, type guards) - you struggled with type safety in [specific project]"
    • "Error handling and validation - I noticed you patched several bugs related to missing null checks"
    • "Async/await patterns - your recent work shows some race conditions and timing issues"
    • "Database query optimization - you rewrote the same query multiple times"
  4. Generate Report
    Create a comprehensive report with this structure:
    markdown
    # Your Developer Growth Report

**Report Period**: [Yesterday / Today / [Custom Date Range]]
**Last Updated**: [Current Date and Time]

## Work Summary

[2-3 paragraphs summarizing what the user worked on, projects touched, technologies used, and overall focus areas]

Example:
"Over the past 24 hours, you focused primarily on backend development with three distinct projects. Your work involved TypeScript, React, and deployment infrastructure. You tackled a mix of feature implementation, debugging, and architectural decisions, with a particular focus on API design and database optimization."

## Improvement Areas (Prioritized)

### 1. [Area Name]

**Why This Matters**: [Explanation of why this skill is important for the user's work]

**What I Observed**: [Specific evidence from chat history showing this gap]

**Recommendation**: [Concrete step(s) to improve in this area]

**Time to Skill Up**: [Brief estimate of effort required]

---

[Repeat for 2-4 additional areas]

## Strengths Observed

[2-3 bullet points highlighting things you're doing well - things to continue doing]

## Action Items

Priority order:
1. [Action item derived from highest priority improvement area]
2. [Action item from next area]
3. [Action item from next area]

## Learning Resources

[Will be populated in next step]
  5. Search for Learning Resources
    Use Rube MCP to search HackerNews for articles related to each improvement area:
    • For each improvement area, construct a search query targeting high-quality resources
    • Search HackerNews using RUBE_SEARCH_TOOLS with queries like:
      • "Learn [Technology/Pattern] best practices"
      • "[Technology] advanced patterns and techniques"
      • "Debugging [specific problem type] in [language]"
    • Prioritize posts with high engagement (comments, upvotes)
    • For each area, include 2-3 most relevant articles with:
      • Article title
      • Publication date
      • Brief description of why it's relevant
      • Link to the article
    Add this section to the report:
    markdown
    ## Curated Learning Resources

### For: [Improvement Area]

1. **[Article Title]** - [Date]
   [Description of what it covers and why it's relevant to your improvement area]
   [Link]

2. **[Article Title]** - [Date]
   [Description]
   [Link]

[Repeat for other improvement areas]
  6. Present the Complete Report
    Deliver the report in a clean, readable format that the user can:
    • Quickly scan for key takeaways
    • Use for focused learning planning
    • Reference over the next week as they work on improvements
    • Share with mentors if they want external feedback
  7. Send Report to Slack DMs
    Use Rube MCP to send the complete report to the user's own Slack DMs:
    • Check if Slack connection is active via RUBE_SEARCH_TOOLS
    • If not connected, use RUBE_MANAGE_CONNECTIONS to initiate Slack auth
    • Use RUBE_MULTI_EXECUTE_TOOL to send the report as a formatted message:
      • Send the report title and period as the first message
      • Break the report into logical sections (Summary, Improvements, Strengths, Actions, Resources)
      • Format each section as a well-structured Slack message with proper markdown
      • Include clickable links for the learning resources
    • Confirm delivery in the CLI output
    This ensures the user has the report in a place they check regularly and can reference it throughout the week.
当用户请求分析其近期工作的开发者成长或编码模式时：
  1. 访问聊天记录
    读取
    ~/.claude/history.jsonl
    中的聊天记录。此文件为JSONL格式，每行包含：
    • display
      ：用户的消息/请求
    • project
      ：正在处理的项目
    • timestamp
      ：Unix时间戳（毫秒）
    • pastedContents
      ：粘贴的任何代码或内容
    根据当前时间戳筛选过去24-48小时内的条目。
  2. 分析工作模式
    从筛选后的聊天记录中提取并分析以下内容：
    • 项目与领域：用户正在处理的项目类型？（例如：后端、前端、DevOps、数据等）
    • 使用的技术：对话中出现的语言、框架和工具？
    • 问题类型：正在解决的问题类别？（例如：性能优化、调试、功能实现、重构、设置/配置）
    • 遇到的挑战：用户遇到了哪些问题？关注：
      • 关于相似主题的重复提问
      • 多次尝试才解决的问题
      • 表明知识短板的问题
      • 复杂的架构决策
    • 处理模式：用户如何解决问题？（例如：有条理、探索性、实验性）
  3. 识别可改进领域
    基于分析结果，识别3-5个用户可以改进的具体领域。这些领域应：
    • 具体（而非“提高编码技能”这类模糊表述）
    • 有依据（基于实际聊天记录）
    • 可操作（可以实际实施的改进措施）
    • 分优先级（影响最大的排在前面）
    优秀的可改进领域示例：
    • "高级TypeScript模式（泛型、工具类型、类型守卫）- 您在[具体项目]中遇到了类型安全相关的问题"
    • "错误处理与验证 - 我注意到您修复了多个与缺失空值检查相关的bug"
    • "Async/await模式 - 您近期的工作存在一些竞态条件和时序问题"
    • "数据库查询优化 - 您多次重写了同一个查询"
  4. 生成报告
    创建一份结构如下的全面报告：
    markdown
    # 您的开发者成长报告

**报告周期**：[昨天 / 今天 / [自定义日期范围]]
**最后更新**：[当前日期和时间]

## 工作总结

[2-3段文字总结用户的工作内容、涉及的项目、使用的技术以及整体聚焦领域]

示例：
"在过去24小时内，您主要专注于三个不同项目的后端开发工作。您使用了TypeScript、React和部署基础设施，处理了功能实现、调试和架构决策等多种任务，尤其关注API设计和数据库优化。"

## 可改进领域（按优先级排序）

### 1. [领域名称]

**重要性**：[解释该技能对用户工作的重要性]

**我的观察**：[来自聊天记录的具体证据，表明存在此短板]

**建议**：[提升该领域的具体步骤]

**学习所需时间**：[大致的精力投入估算]

---

[重复2-4个其他领域]

## 已观察到的优势

[2-3个要点，突出用户做得好的地方 - 需要继续保持的事项]

## 行动项

优先级排序：
1. [来自最高优先级可改进领域的行动项]
2. [来自下一个领域的行动项]
3. [来自下一个领域的行动项]

## 学习资源

[将在下一步填充]
  5. 搜索学习资源
    使用Rube MCP在HackerNews上搜索与每个可改进领域相关的文章：
    • 针对每个可改进领域，构造聚焦高质量资源的搜索查询
    • 使用RUBE_SEARCH_TOOLS在HackerNews上搜索，例如：
      • "Learn [Technology/Pattern] best practices"
      • "[Technology] advanced patterns and techniques"
      • "Debugging [specific problem type] in [language]"
    • 优先选择参与度高（评论、点赞多）的帖子
    • 针对每个领域，包含2-3个最相关的文章，信息包括：
      • 文章标题
      • 发布日期
      • 简短说明其相关性
      • 文章链接
    将以下部分添加到报告中：
    markdown
    ## 精选学习资源

### 针对：[可改进领域]

1. **[文章标题]** - [日期]
   [说明文章内容及其与您可改进领域的相关性]
   [链接]

2. **[文章标题]** - [日期]
   [说明]
   [链接]

[重复其他可改进领域]
  6. 呈现完整报告
    以清晰易读的格式交付报告，方便用户：
    • 快速浏览关键要点
    • 用于制定聚焦的学习计划
    • 在接下来的一周内参考，以改进工作
    • 如果需要外部反馈，可以与导师分享
  7. 发送报告至Slack私信
    使用Rube MCP将完整报告发送至用户的Slack私信：
    • 通过RUBE_SEARCH_TOOLS检查Slack连接是否活跃
    • 如果未连接，使用RUBE_MANAGE_CONNECTIONS启动Slack授权
    • 使用RUBE_MULTI_EXECUTE_TOOL将报告作为格式化消息发送：
      • 将报告标题和周期作为第一条消息发送
      • 将报告拆分为逻辑部分（总结、改进点、优势、行动项、资源）
      • 将每个部分格式化为结构清晰的Slack消息，使用正确的markdown
      • 为学习资源添加可点击的链接
    • 在CLI输出中确认交付成功
    这样可以确保用户在经常查看的地方收到报告，并能在一周内随时参考。

Example Usage

示例用法

Input

输入

Analyze my developer growth from my recent chats
Analyze my developer growth from my recent chats

Output

输出

markdown
undefined
markdown
undefined

Your Developer Growth Report

您的开发者成长报告

Report Period: November 9-10, 2024 Last Updated: November 10, 2024, 9:15 PM UTC
报告周期：2024年11月9-10日 最后更新：2024年11月10日 晚上9:15 UTC

Work Summary

工作总结

Over the past two days, you focused on backend infrastructure and API development. Your primary project was an open-source showcase application, where you made significant progress on connections management, UI improvements, and deployment configuration. You worked with TypeScript, React, and Node.js, tackling challenges ranging from data security to responsive design. Your work shows a balance between implementing features and addressing technical debt.
在过去两天里，您专注于后端基础设施和API开发。您的主要项目是一个开源展示应用，在连接管理、UI改进和部署配置方面取得了显著进展。您使用了TypeScript、React和Node.js，处理了从数据安全到响应式设计的各类挑战。您的工作在功能实现和技术债务处理之间取得了平衡。

Improvement Areas (Prioritized)

可改进领域（按优先级排序）

1. Advanced TypeScript Patterns and Type Safety

1. 高级TypeScript模式与类型安全

Why This Matters: TypeScript is central to your work, but leveraging its advanced features (generics, utility types, conditional types, type guards) can significantly improve code reliability and reduce runtime errors. Better type safety catches bugs at compile time rather than in production.
What I Observed: In your recent chats, you were working with connection data structures and struggled a few times with typing auth configurations properly. You also had to iterate on union types for different connection states. There's an opportunity to use discriminated unions and type guards more effectively.
Recommendation: Study TypeScript's advanced type system, particularly utility types (Omit, Pick, Record), conditional types, and discriminated unions. Apply these patterns to your connection configuration handling and auth state management.
Time to Skill Up: 5-8 hours of focused learning and practice
重要性：TypeScript是您工作的核心，但利用其高级特性（泛型、工具类型、类型守卫）可以显著提高代码可靠性，减少运行时错误。更好的类型安全可以在编译时捕获bug，而非等到生产环境。
我的观察：在您近期的聊天记录中，您处理连接数据结构时多次遇到类型配置相关的问题。您还需要迭代不同连接状态的联合类型。您可以更有效地使用判别联合和类型守卫。
建议：学习TypeScript的高级类型系统，尤其是工具类型（Omit、Pick、Record）、条件类型和判别联合。将这些模式应用到您的连接配置处理和认证状态管理中。
学习所需时间：5-8小时的聚焦学习与实践

2. Secure Data Handling and Information Hiding in UI

2. UI中的安全数据处理与信息隐藏

Why This Matters: You identified and fixed a security concern where sensitive connection data was being displayed in your console. Preventing information leakage is critical for applications handling user credentials and API keys. Good practices here prevent security incidents and user trust violations.
What I Observed: You caught that your "Your Apps" page was showing full connection data including auth configs. This shows good security instincts, and the next step is building this into your default thinking when handling sensitive information.
Recommendation: Review security best practices for handling sensitive data in frontend applications. Create reusable patterns for filtering/masking sensitive information before displaying it. Consider implementing a secure data layer that explicitly whitelist what can be shown in the UI.
Time to Skill Up: 3-4 hours
重要性：您发现并修复了一个安全问题，即敏感连接数据被显示在控制台中。防止信息泄露对于处理用户凭据和API密钥的应用至关重要。良好的实践可以防止安全事件和用户信任受损。
我的观察：您发现“您的应用”页面显示了包括认证配置在内的完整连接数据。这表明您有良好的安全直觉，下一步是将此融入处理敏感信息时的默认思维。
建议：回顾前端应用处理敏感数据的安全最佳实践。创建可复用的模式，在显示敏感信息前进行过滤/掩码处理。考虑实现一个明确白名单可在UI中显示内容的安全数据层。
学习所需时间：3-4小时

3. Component Architecture and Responsive UI Patterns

3. 组件架构与响应式UI模式

Why This Matters: You're designing UIs that need to work across different screen sizes and user interactions. Strong component architecture makes it easier to build complex UIs without bugs and improves maintainability.
What I Observed: You worked on the "Marketplace" UI (formerly Browse Tools), recreating it from a design image. You also identified and fixed scrolling issues where content was overflowing containers. There's an opportunity to strengthen your understanding of layout containment and responsive design patterns.
Recommendation: Study React component composition patterns and CSS layout best practices (especially flexbox and grid). Focus on container queries and responsive patterns that prevent overflow issues. Look into component composition libraries and design system approaches.
Time to Skill Up: 6-10 hours (depending on depth)
重要性：您正在设计需要适配不同屏幕尺寸和用户交互的UI。强大的组件架构可以更轻松地构建无bug的复杂UI，并提高可维护性。
我的观察：您重新设计了“市场”UI（原浏览工具），根据设计图进行了重构。您还发现并修复了内容溢出容器的滚动问题。您可以加强对布局包含和响应式设计模式的理解。
建议：学习React组件组合模式和CSS布局最佳实践（尤其是flexbox和grid）。关注容器查询和防止溢出问题的响应式模式。研究组件组合库和设计系统方法。
学习所需时间：6-10小时（取决于学习深度）

Strengths Observed

已观察到的优势

  • Security Awareness: You proactively identified data leakage issues before they became problems
  • Iterative Refinement: You worked through UI requirements methodically, asking clarifying questions and improving designs
  • Full-Stack Capability: You comfortably work across backend APIs, frontend UI, and deployment concerns
  • Problem-Solving Approach: You break down complex tasks into manageable steps
  • 安全意识：您在问题发生前主动发现了数据泄露问题
  • 迭代优化：您有条理地处理UI需求，提出澄清问题并改进设计
  • 全栈能力：您可以轻松处理后端API、前端UI和部署相关问题
  • 解决问题的方法：您将复杂任务分解为可管理的步骤

Action Items

行动项

Priority order:
  1. Spend 1-2 hours learning TypeScript utility types and discriminated unions; apply to your connection data structures
  2. Document security patterns for your project (what data is safe to display, filtering/masking functions)
  3. Study one article on advanced React patterns and apply one pattern to your current UI work
  4. Set up a code review checklist focused on type safety and data security for future PRs
优先级排序：
  1. 花费1-2小时学习TypeScript工具类型和判别联合；将其应用到您的连接数据结构中
  2. 记录项目的安全模式（哪些数据可以安全显示、过滤/掩码函数）
  3. 学习一篇关于高级React模式的文章，并将其中一种模式应用到您当前的UI工作中
  4. 为未来的PR建立一个聚焦类型安全和数据安全的代码审查清单

Curated Learning Resources

精选学习资源

For: Advanced TypeScript Patterns

针对：高级TypeScript模式

  1. TypeScript's Advanced Types: Generics, Utility Types, and Conditional Types - HackerNews, October 2024 Deep dive into TypeScript's type system with practical examples and real-world applications. Covers discriminated unions, type guards, and patterns for ensuring compile-time safety in complex applications. [Link to discussion]
  2. Building Type-Safe APIs in TypeScript - HackerNews, September 2024 Practical guide to designing APIs with TypeScript that catch errors early. Particularly relevant for your connection configuration work. [Link to discussion]
  1. TypeScript's Advanced Types: Generics, Utility Types, and Conditional Types - HackerNews, 2024年10月 深入讲解TypeScript类型系统，包含实用示例和真实应用场景。涵盖判别联合、类型守卫以及确保复杂应用编译时安全的模式。 [讨论链接]
  2. Building Type-Safe APIs in TypeScript - HackerNews, 2024年9月 实用指南，介绍如何用TypeScript设计可提前捕获错误的API。与您的连接配置工作特别相关。 [讨论链接]

For: Secure Data Handling in Frontend

针对：前端安全数据处理

  1. Preventing Information Leakage in Web Applications - HackerNews, August 2024 Comprehensive guide to data security in frontend applications, including filtering sensitive information, secure logging, and audit trails. [Link to discussion]
  2. OAuth and API Key Management Best Practices - HackerNews, July 2024 How to safely handle authentication tokens and API keys in applications, with examples for different frameworks. [Link to discussion]
  1. Preventing Information Leakage in Web Applications - HackerNews, 2024年8月 前端应用数据安全的综合指南，包含敏感信息过滤、安全日志和审计追踪等内容。 [讨论链接]
  2. OAuth and API Key Management Best Practices - HackerNews, 2024年7月 如何在应用中安全处理认证令牌和API密钥，包含不同框架的示例。 [讨论链接]

For: Component Architecture and Responsive Design

针对：组件架构与响应式设计

  1. Advanced React Patterns: Composition Over Configuration - HackerNews Explores component composition strategies that scale, with examples using modern React patterns. [Link to discussion]
  2. CSS Layout Mastery: Flexbox, Grid, and Container Queries - HackerNews, October 2024 Learn responsive design patterns that prevent overflow issues and work across all screen sizes. [Link to discussion]
undefined
  1. Advanced React Patterns: Composition Over Configuration - HackerNews 探讨可扩展的组件组合策略，包含使用现代React模式的示例。 [讨论链接]
  2. CSS Layout Mastery: Flexbox, Grid, and Container Queries - HackerNews, 2024年10月 学习可防止溢出问题、适配所有屏幕尺寸的响应式设计模式。 [讨论链接]
undefined

Tips and Best Practices

提示与最佳实践

  • Run this analysis once a week to track your improvement trajectory over time
  • Pick one improvement area at a time and focus on it for a few days before moving to the next
  • Use the learning resources as a study guide; work through the recommended materials and practice applying the patterns
  • Revisit this report after focusing on an area for a week to see how your work patterns change
  • The learning resources are intentionally curated for your actual work, not generic topics, so they'll be highly relevant to what you're building
  • 每周运行一次此分析，跟踪您的成长轨迹
  • 一次专注于一个改进领域，花几天时间学习后再转向下一个
  • 将学习资源作为学习指南；通读推荐材料并实践应用相关模式
  • 在专注一个领域一周后重新查看此报告，观察您的工作模式变化
  • 学习资源是根据您的实际工作精心筛选的，而非通用主题，因此与您正在构建的内容高度相关

How Accuracy and Quality Are Maintained

如何保持准确性与质量

This skill:
  • Analyzes your actual work patterns from timestamped chat history
  • Generates evidence-based recommendations grounded in real projects
  • Curates learning resources that directly address your identified gaps
  • Focuses on actionable improvements, not vague feedback
  • Provides specific time estimates based on complexity
  • Prioritizes areas that will have the most impact on your development velocity
该Skill：
  • 分析带时间戳的聊天记录中的实际工作模式
  • 基于真实项目生成有依据的建议
  • 筛选直接针对您已识别短板的学习资源
  • 聚焦可操作的改进，而非模糊的反馈
  • 根据复杂度提供具体的时间估算
  • 优先选择对您的开发效率影响最大的领域