mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
054c0e56e9
Removed the deprecated 'model: sonnet' field from command frontmatter to fix compatibility issues with Claude Code. Commands will now inherit the model from the active conversation instead of using a hardcoded deprecated model identifier. Changes: - Removed 'model: sonnet' from 142 command files across all categories - Commands now use default model inheritance behavior - Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model) - 67 commands without model field remain unchanged This resolves the "model: sonnet not found" error reported in GitHub issues and aligns with Claude Code's recommended practice of letting commands inherit the conversation model. Affected categories: - Database/Supabase commands (8 files) - Documentation commands (8 files) - Deployment commands (11 files) - Setup commands (14 files) - Performance commands (8 files) - Team commands (14 files) - Security commands (6 files) - NextJS/Vercel commands (10 files) - Sync commands (14 files) - And more across other categories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.1 KiB
2.1 KiB
allowed-tools: Read, Write, Bash
argument-hint: [scope] | --github-issues | --linear-tasks | --priority-analysis | --team-assignment
description: Intelligent issue triage with automatic categorization, prioritization, and team assignment
Issue Triage
Intelligently triage and prioritize issues with automated routing and team assignment: $ARGUMENTS
Current Triage Context
- Repository: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context" - Open issues: !
gh issue list --state open --limit 1 --json number | jq length 2>/dev/null || echo "Check manually" - Linear teams: Available Linear teams and project assignments for routing
- Triage backlog: Current volume and age of untriaged issues
Task
Execute intelligent issue analysis with automated triage and priority assignment:
Triage Scope: Use $ARGUMENTS to focus on GitHub issues, Linear tasks, priority analysis, or team assignment optimization
Triage Framework:
- Issue Analysis - Extract issue metadata, analyze content patterns, assess severity indicators, evaluate impact scope
- Category Classification - Identify issue type (bug, feature, documentation), assess complexity level, determine urgency factors
- Priority Assessment - Calculate priority score using severity, impact, effort, and business value metrics
- Team Routing - Match issue skills to team expertise, balance workload distribution, consider current sprint capacity
- Label Management - Apply consistent labeling scheme, maintain taxonomy standards, enable filtering and reporting
- SLA Assignment - Set response time expectations, establish resolution targets, track performance metrics
Advanced Features: Automated severity detection, intelligent team matching, workload balancing, SLA monitoring, escalation workflows.
Quality Assurance: Consistency validation, triage accuracy tracking, team satisfaction monitoring, process optimization feedback.
Output: Complete issue triage with priority assignments, team routing recommendations, SLA targets, and process improvement insights.