developer-growth-analysis

开发者成长分析

此技能通过分析你最近与 Codex 的聊天互动，识别体现优势和成长空间的模式，从而为你的近期编码工作提供个性化反馈。

何时使用此技能

在以下情况下使用此技能：

• 了解你近期工作中的开发模式和习惯
• 发现具体的技术短板或反复遇到的挑战
• 找出值得深入学习的主题
• 获取根据你的实际工作模式定制的精选学习资源
• 跟踪近期项目中的提升方向
• 查找能够直接提升你正在培养的技能的优质文章

此技能非常适合希望获得有条理的成长反馈、不想等候代码审查，并且倾向于从自身工作记录中获取数据驱动见解的开发者。

此技能的功能

此技能会分六个步骤分析你的开发工作：

1. 读取聊天记录：访问你过去 24-48 小时的本地 Codex 聊天记录，了解你一直在处理哪些工作。

2. 识别开发模式：分析你正在解决的问题类型、使用的技术、遇到的挑战，以及你处理不同类型任务的方式。

3. 发现提升方向：识别可能表明存在技能短板、反复受挫、方法效率低下，或值得深入学习的模式。

4. 生成个性化报告：创建一份全面的报告，展示你的工作摘要、发现的提升方向，以及具体的成长建议。

5. 查找学习资源：使用 HackerNews 精选与提升方向直接相关的优质文章和讨论，为你提供根据实际开发工作定制的阅读清单。

6. 发送到你的 Slack 私信：自动将完整报告发送到你自己的 Slack 私信，方便你随时随地查看。

使用方法

请 Codex 分析你近期的编码工作：

Analyze my developer growth from my recent chats

也可以明确指定时间范围：

Analyze my work from today and suggest areas for improvement

此技能将生成格式化报告，其中包括：

• 近期工作概览
• 发现的主要提升方向
• 针对每个方向的具体建议
• HackerNews 精选学习资源
• 你可以着重处理的行动事项

指令

当用户请求分析其近期工作中的开发者成长或编码模式时：

1. 访问聊天记录

   从 $CODEX_HOME/history.jsonl（默认为 ~/.codex/history.jsonl）读取聊天记录。此文件采用 JSONL 格式，每行包含：

   • display：用户的消息/请求
   • project：正在处理的项目
   • timestamp：Unix 时间戳（以毫秒为单位）
   • pastedContents：粘贴的代码或内容

   根据当前时间戳筛选过去 24-48 小时内的条目。

2. 分析工作模式

   从筛选后的聊天记录中提取并分析以下内容：

   • 项目和领域：用户正在处理哪些类型的项目？（例如，后端、前端、DevOps、数据等）
   • 使用的技术：对话中出现了哪些语言、框架和工具？
   • 问题类型：正在解决哪些类别的问题？（例如，性能优化、调试、功能实现、重构、设置/配置）
   • 遇到的挑战：用户在哪些问题上遇到困难？注意以下迹象：
     • 多次询问相似主题
     • 需要多次尝试才能解决的问题
     • 表明存在知识盲区的问题
     • 复杂的架构决策
   • 解决问题的模式：用户如何解决问题？（例如，有条理、探索式、实验式）

3. 识别提升方向 基于分析，找出 3-5 个用户可以提高的具体领域。这些领域应当：

   • 具体（不要像“提高编码能力”这样含糊）
   • 有依据（基于实际聊天记录）
   • 可执行（可以做出的实际改进）
   • 按优先级排序（影响最大的排在前面）

   优秀改进领域的示例：

   • “高级 TypeScript 模式（泛型、工具类型、类型守卫）——你在 [具体项目] 中遇到了类型安全方面的问题”
   • “错误处理与验证——我注意到你修复了几个与缺少空值检查相关的 bug”
   • “Async/await 模式——你最近的工作显示出一些竞态条件和时序问题”
   • “数据库查询优化——你多次重写了同一个查询”

4. 生成报告

   按以下结构创建一份全面的报告：

   # 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. 搜索学习资源

   使用 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 篇最相关的文章，并附上：
     • 文章标题
     • 发布日期
     • 简要说明其为何相关
     • 文章链接

   将本节添加到报告中：

   ## 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. 呈现完整报告

   以简洁、易读的格式交付报告，使用户能够：

   • 快速浏览关键要点
   • 用于制定有针对性的学习计划
   • 在接下来一周推进改进时随时参考
   • 如需外部反馈，可分享给导师

7. 将报告发送到 Slack 私信

   使用 Rube MCP 将完整报告发送到用户自己的 Slack 私信：

   • 通过 RUBE_SEARCH_TOOLS 检查 Slack 连接是否处于活动状态
   • 如果未连接，使用 RUBE_MANAGE_CONNECTIONS 发起 Slack 认证
   • 使用 RUBE_MULTI_EXECUTE_TOOL 将报告作为格式化消息发送：
     • 将报告标题和周期作为第一条消息发送
     • 将报告拆分为逻辑清晰的部分（Summary、Improvements、Strengths、Actions、Resources）
     • 将每个部分格式化为结构良好的 Slack 消息，并使用适当的 markdown
     • 为学习资源添加可点击链接
   • 在命令行输出中确认发送成功

   这可确保用户在他们经常查看的地方收到报告，并在整周内都能参考它。

示例用法

输入

Analyze my developer growth from my recent chats

输出

# Your Developer Growth Report

**Report Period**: November 9-10, 2024
**Last Updated**: November 10, 2024, 9:15 PM 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.

## Improvement Areas (Prioritized)

### 1. Advanced TypeScript Patterns and Type Safety

**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

### 2. Secure Data Handling and Information Hiding in 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

### 3. Component Architecture and Responsive UI Patterns

**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)

## 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

## 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

## Curated Learning Resources

### For: Advanced TypeScript Patterns

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]

### 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]

### 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]

提示与最佳实践

• 每周运行一次此分析，以跟踪你随时间推移的改进轨迹
• 每次只选择一个改进领域，专注几天后再转向下一个
• 将学习资源用作学习指南；完成推荐材料，并练习应用这些模式
• 在专注某个领域一周后重新查看此报告，看看你的工作模式如何变化
• 学习资源是专门根据你的实际工作策划的，而不是泛泛的主题，因此它们会与你正在构建的内容高度相关

如何保持准确性与质量

此技能：

• 根据带时间戳的聊天记录分析你的实际工作模式
• 生成基于真实项目的、有依据的建议
• 策划直接针对你所识别差距的学习资源
• 专注于可执行的改进，而不是含糊的反馈
• 根据复杂度提供具体的时间估计
• 优先考虑对你的开发速度影响最大的领域