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.5 KiB
1.5 KiB
allowed-tools: Read, Bash, Grep, Glob
argument-hint: [project-description] | --team-id | --create-new | --epic-name
description: Sync project structure and requirements to Linear workspace with comprehensive task breakdown
Project to Linear
Sync project structure and requirements to Linear workspace: $ARGUMENTS
Linear Integration Status
- Linear MCP: Check if Linear MCP server is configured
- Workspace access: !
echo "Test Linear connection if MCP available" - Project context: @README.md or project documentation
- Requirements: Based on $ARGUMENTS analysis
Task
Analyze project requirements and create comprehensive Linear task structure:
Project Analysis Process:
- Requirement Analysis - Parse project description and identify major components
- Task Breakdown - Create hierarchical task structure with epics and subtasks
- Dependency Mapping - Identify task dependencies and critical path
- Linear Integration - Create project, epics, and tasks in Linear workspace
- Validation - Review created structure and provide project overview
Task Organization:
- Epic-level features and major components
- Parent tasks for feature areas
- Detailed subtasks with acceptance criteria
- Proper labeling (frontend, backend, testing, documentation)
- Priority and effort estimates
- Timeline and dependency relationships
Output: Complete Linear project structure with organized task hierarchy, clear descriptions, and actionable items.