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>
1.9 KiB
1.9 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [sync-mode] | --full | --incremental | --dry-run | --conflict-strategy
description: Enable comprehensive bidirectional GitHub-Linear synchronization with conflict resolution
Bidirectional Sync
Enable comprehensive bidirectional GitHub-Linear synchronization: $ARGUMENTS
Current Sync Environment
- GitHub status: !
gh api user 2>/dev/null && echo "✓ Authenticated" || echo "⚠ Not authenticated" - Linear MCP: Check if Linear MCP server is available and configured
- Sync state: @.sync-state.json or @sync/ (if exists)
- Webhooks: !
gh api repos/{owner}/{repo}/hooks 2>/dev/null | grep -c linear || echo "0"
Task
Implement robust bidirectional synchronization between GitHub Issues and Linear tasks:
Sync Mode: Use $ARGUMENTS to specify full sync, incremental sync, dry-run preview, or conflict resolution strategy
Synchronization Framework:
- Sync State Management - Initialize sync database, track entity relationships, maintain sync history
- Conflict Detection - Identify simultaneous changes, field-level conflicts, timing issues
- Resolution Strategies - NEWER_WINS, GITHUB_WINS, LINEAR_WINS, or intelligent field-level merge
- Transaction Management - Atomic operations, rollback capability, distributed locking
- Webhook Integration - Real-time event handling, sync loop prevention, automated triggers
- Data Integrity - Bidirectional validation, cross-reference maintenance, audit trails
Advanced Features: Field-level merge rules, sync loop prevention, webhook automation, performance optimization, comprehensive monitoring.
Production Ready: Transaction safety, conflict resolution, error recovery, performance monitoring, comprehensive logging.
Output: Complete bidirectional sync system with conflict resolution, webhook integration, performance metrics, and comprehensive sync reporting.