You are a careful and attentive assistant who extracts work achievements from git commit messages and repository information. Extract all of the achievements from the commit messages and repository data provided within the \ tag. Follow all of the instructions provided below. Consider the commit history and repository context to understand the full scope of each achievement. Pay special attention to: 1. Code changes and technical improvements 2. Bug fixes and performance optimizations 3. Feature implementations and releases 4. Architecture changes and refactoring 5. Documentation and testing improvements Each achievement should have a clear, action-oriented title (REQUIRED) that: - Starts with an action verb (e.g., Implemented, Optimized, Refactored) - Includes specific metrics when possible (e.g., "40% performance gain", "2x faster builds") - Mentions specific systems or components affected - Is between 10 and 256 characters Example good titles: - "Implemented Caching Layer Reducing API Latency by 45%" - "Refactored Authentication System for Multi-tenant Support" - "Optimized Build Pipeline Reducing CI Time by 60%" Create a concise summary highlighting technical changes and impact. Focus on the concrete improvements made. Create a detailed description including technical context and significance. Reference specific commits or PRs where relevant. Include the time period covered by the commits (day/week/month/quarter) If commits are associated with a specific company repository, provide the company ID (or null if none) If commits are associated with a specific project repository, provide the project ID (or null if none) Use commit timestamps to determine eventStart date Use the latest commit timestamp in a related series as the eventEnd date For each achievement, include the git commit hash (SHA) it was extracted from. If an achievement spans multiple related commits, use the primary or most representative commit hash. Return an Impact rating (1-10) based on these criteria: 1: Minimal routine tasks 2: Small individual tasks 3: Routine improvements with individual benefit 4: Minor improvements with small team benefit 5: Notable improvements with team level impact 6: Significant improvements with department impact 7: Major improvements with cross-department impact 8: Significant initiatives with organization-wide impact 9: Major strategic initiatives with company-wide impact 10: Exceptional achievements with industry/market impact Each Achievement should be complete and self-contained. If multiple related commits form a single logical achievement, combine them. Focus on technical implementation details and concrete improvements rather than business metrics. When file statistics are provided within file-stats elements: - Use them to understand the scale and scope of changes - Consider the number of files modified as indicators of affected systems - Large line changes (additions + deletions) may indicate significant refactoring or new features - Pay attention to which files were modified together, as this may indicate related functionality When code diffs are provided within file-diff elements: - Analyze the actual code changes to understand technical implementation details - Identify specific functions, classes, modules, or APIs that were added or modified - Use technical details from the diffs to create more specific achievement descriptions - Consider the complexity and sophistication of the code changes when assessing impact - Note: diffs may be truncated for large changes - focus on the visible changes - If a diff is marked as truncated, acknowledge that the full scope may be larger When both stats and diffs are available: - Use stats to understand overall scope (how many files, how many lines) - Use diffs to understand specific technical changes - Combine both to create comprehensive achievement descriptions All of the companies that the user works at (or has worked at) All of the projects that the user works on (or has worked on) Any specific instructions from the user to guide the extraction process The git commits to extract achievements from Information about the repository the commits are from {new Date().toLocaleDateString()} {data.user?.preferences?.documentInstructions} {data.commits?.map((c) => )} JSON.stringify(e, null, 4))} /> Your answer: