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
1.9 KiB
Markdown
36 lines
1.9 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [sync-scope] | --team | --project | --priority | --states
|
|
description: Sync Linear tasks to GitHub issues with state mapping and attachment handling
|
|
---
|
|
|
|
# Sync Linear to Issues
|
|
|
|
Sync Linear tasks to GitHub issues with comprehensive state and field mapping: **$ARGUMENTS**
|
|
|
|
## Current Linear Context
|
|
|
|
- Linear teams: Available teams and project assignments
|
|
- Task count: Linear task query to determine scope
|
|
- Target repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context"`
|
|
- User mappings: Linear email to GitHub username correspondence
|
|
|
|
## Task
|
|
|
|
Execute comprehensive synchronization of Linear tasks to GitHub issues:
|
|
|
|
**Sync Scope**: Use $ARGUMENTS to filter by Linear team, project, priority levels, or task states
|
|
|
|
**Synchronization Framework**:
|
|
1. **Task Discovery** - Query Linear tasks with filters, extract metadata, validate requirements, prioritize sync
|
|
2. **State Mapping** - Transform Linear states to GitHub equivalents, handle priority conversion, map project assignments
|
|
3. **Content Transformation** - Build GitHub issue body, preserve formatting, handle attachments, maintain structure
|
|
4. **GitHub Integration** - Create issues with proper labels, assign users, set milestones, manage relationships
|
|
5. **Attachment Migration** - Download Linear attachments, upload to GitHub, update references, maintain accessibility
|
|
6. **Comment Synchronization** - Transfer comments with attribution, preserve context, handle mentions, maintain threading
|
|
|
|
**Advanced Features**: Intelligent state mapping, attachment handling, comment threading, user mention translation, comprehensive validation.
|
|
|
|
**Data Fidelity**: Preserve Linear formatting, maintain task relationships, keep timestamps, ensure reference integrity.
|
|
|
|
**Output**: Complete synchronization results with created issues, attachment migrations, comment transfers, and comprehensive sync reporting. |