mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Dani
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>
36 lines
2.1 KiB
Markdown
36 lines
2.1 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [task-id] | --repo | --milestone | --close-linear | --skip-attachments
|
|
description: Convert Linear tasks to GitHub issues with relationship preservation and metadata mapping
|
|
---
|
|
|
|
# Linear Task to Issue
|
|
|
|
Convert Linear tasks to GitHub issues with comprehensive relationship mapping: **$ARGUMENTS**
|
|
|
|
## Current Task Context
|
|
|
|
- Task details: Based on $ARGUMENTS task identifier or selection criteria
|
|
- Target repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context"`
|
|
- User mappings: Linear email to GitHub username correspondence
|
|
- Attachment handling: Linear attachment access and GitHub upload capabilities
|
|
|
|
## Task
|
|
|
|
Execute precise conversion of Linear tasks to GitHub issues:
|
|
|
|
**Task Target**: Use $ARGUMENTS to specify task identifier, target repository, milestone mapping, or processing preferences
|
|
|
|
**Conversion Framework**:
|
|
1. **Task Analysis** - Fetch complete Linear task data, extract relationships, analyze content structure, identify priorities
|
|
2. **Content Transformation** - Build GitHub issue body, map Linear fields, preserve formatting, handle rich content
|
|
3. **GitHub Integration** - Create issue with proper structure, apply labels, assign users, set milestones, manage relationships
|
|
4. **Attachment Migration** - Download Linear attachments, upload to GitHub, update references, maintain accessibility
|
|
5. **Comment Import** - Transfer comments with attribution, preserve timestamps, maintain context, handle mentions
|
|
6. **Cross-Reference Setup** - Create bidirectional links, update Linear task, maintain sync database, enable navigation
|
|
|
|
**Advanced Features**: Rich content conversion, attachment handling, relationship mapping, user mention translation, comprehensive validation.
|
|
|
|
**Relationship Management**: Preserve parent-child relationships, maintain team context, map project associations, handle dependencies.
|
|
|
|
**Output**: Successfully created GitHub issue with complete data migration, accurate field mappings, preserved relationships, and comprehensive conversion report. |