feat: enhance autolabeler to handle issues, improvements, and feature requests

- Update component identification to cover issues/improvements/features for all components
- Clarify team member responsibilities include improvement opportunities and feature requests
- Ensure comprehensive coverage of all types of GitHub issues beyond just bugs

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: maxprilutskiy

.github/workflows/claude-issue-autolabel.yml

@@ -66,32 +66,48 @@ jobs:
 
             EXECUTION PROTOCOL - FOLLOW EVERY STEP:
 
-            1. CONTRIBUTOR ANALYSIS (MANDATORY):
+            1. COMPONENT IDENTIFICATION (MANDATORY):
+               Analyze the issue title and body to determine which lingo.dev component this relates to:
+               - JS SDK: API integration, SDK usage, authentication issues/improvements/features
+               - CLI: File management, localization workflows, CLI commands, CI/CD integration issues/improvements/features
+               - Compiler: React app localization, build-time string extraction, webpack/vite integration issues/improvements/features
+               - AI/Translation Quality: Translation accuracy, language support, AI-powered features/improvements
+               - Docs/DX: Documentation, developer experience, setup instructions issues/improvements/opportunities
+               - UX: User interface, user experience, design problems/improvements/opportunities
+               
+               Based on component, determine relevant team members:
+               - David (@davidturnbull): docs/dx/instructions questions, improvements, or opportunities
+               - Matej (@mathio): CLI, CI/CD, and Compiler issues, improvements, or features
+               - Veronica (@vrcprl): AI/LLMs and translation quality or languages improvements/features
+               - Dmytro (@pqoqubbw) + Matej (@mathio): UX issues/improvements/opportunities
+               - Max (@maxprilutskiy): everything else, general issues/improvements/features
+
+            2. CONTRIBUTOR ANALYSIS (MANDATORY):
                Execute: `gh search issues --repo ${{ github.repository }} --author ${{ steps.target_issue.outputs.issue_author }} --json number | jq 'length'`
                Determine if first-time or returning contributor.
 
-            2. CODEBASE EXPLORATION (MANDATORY):
+            3. CODEBASE EXPLORATION (MANDATORY):
                Execute these commands in sequence:
                - `find . -name "*.ts" -o -name "*.js" -o -name "*.json" | grep -E "(src|packages|lib)" | head -20`
                - `grep -r "keyword1\|keyword2" src/ packages/ --include="*.ts" --include="*.js" | head -10`
                - `cat CODEOWNERS` (if exists)
                - `find . -name "package.json" | head -5 | xargs cat`
                - `git log --oneline -5 --grep="relevant_keyword"`
 
-            3. ISSUE INTELLIGENCE (MANDATORY):
+            4. ISSUE INTELLIGENCE (MANDATORY):
                Execute these searches:
                - `gh issue list --state open --search "relevant keywords" --json number,title,state | head -3`
                - `gh issue list --state all --search "similar terms" --json number,title,state | head -3`
                - `gh pr list --state open --search "related keywords" --json number,title,state | head -3`
 
-            4. LABELING (MANDATORY):
+            5. LABELING (MANDATORY):
                Apply labels using: `gh issue edit ${{ steps.target_issue.outputs.issue_number }} --add-label "label-name"`
                Must apply:
                - Content labels: bug, enhancement, documentation, question, cli, compiler, etc.
                - State labels: duplicate (if found), wip (if related PR exists)
                - Difficulty labels: "good first issue" (simple, well-defined), "help wanted" (complex/community)
 
-            5. COMMENT GENERATION (MANDATORY):
+            6. COMMENT GENERATION (MANDATORY):
                Post separate comments using: `gh issue comment ${{ steps.target_issue.outputs.issue_number }} --body "text"`
 
                COMMENT TYPES TO POST (only if applicable):
@@ -116,9 +132,17 @@ jobs:
                "This is similar to #[number] - check that for context" OR "There's already work on this in PR #[number]"
 
                G. MAINTAINER ASSESSMENT (post for complex/breaking changes):
-               "Maintainer assessment: [technical analysis]. Suggested approach: [specific steps]. Concerns: [any issues]. Next steps: [actionable items]. Tagging [relevant maintainer if found in CODEOWNERS]."
-
-            6. FINAL STEP (MANDATORY):
+               "Maintainer assessment: [technical analysis]. Suggested approach: [specific steps]. Concerns: [any issues]. Next steps: [actionable items]. Tagging relevant team members based on component identified in step 1."
+               
+               H. TEAM MEMBER TAGGING (post when component identified):
+               Based on component analysis from step 1, tag relevant team members:
+               - Docs/DX issues/improvements/opportunities: "cc @davidturnbull for documentation and developer experience"
+               - CLI/Compiler issues/improvements/features: "cc @mathio for CLI and compiler functionality" 
+               - AI/Translation issues/improvements/features: "cc @vrcprl for AI and translation quality"
+               - UX issues/improvements/opportunities: "cc @pqoqubbw @mathio for UX improvements"
+               - General/Other issues/improvements/features: "cc @maxprilutskiy for general oversight"
+
+            7. FINAL STEP (MANDATORY):
                Execute: `gh issue edit ${{ steps.target_issue.outputs.issue_number }} --add-label "autolabeled"`
 
             ABSOLUTE REQUIREMENTS: