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>
2.3 KiB
2.3 KiB
allowed-tools: Read, Glob, Grep, Bash
argument-hint: [scope] | --tasks | --code | --circular | --critical-path
description: Map project and task dependencies with critical path analysis and circular dependency detection
Dependency Mapper
Map and analyze project dependencies with task ordering optimization: $ARGUMENTS
Current Dependency Context
- Repository: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context" - Project files: !
find . -name "*.js" -o -name "*.ts" -o -name "*.py" | wc -lcode files analyzed - Task tracking: Linear MCP server connectivity and task relationship data
- Import analysis: Code dependency structure and circular dependency detection
Task
Execute comprehensive dependency analysis with optimization recommendations:
Analysis Scope: Use $ARGUMENTS to focus on task dependencies, code dependencies, circular dependency detection, or critical path analysis
Dependency Analysis Framework:
- Code Dependency Mapping - Extract import statements, analyze module relationships, identify coupling levels, map file interdependencies
- Task Relationship Analysis - Query Linear task dependencies, extract task mentions, analyze project relationships, map epic structures
- Dependency Graph Construction - Build comprehensive graph structure, identify dependency chains, calculate critical paths, detect bottlenecks
- Circular Dependency Detection - Implement cycle detection algorithms, identify problematic loops, assess impact severity, recommend resolution strategies
- Execution Order Optimization - Calculate topological sort, optimize task sequence, balance team capacity, minimize blocking dependencies
- Risk Assessment - Identify high-risk chains, assess single points of failure, evaluate dependency complexity, recommend mitigation strategies
Advanced Features: Visual dependency graphs, ASCII tree representations, impact analysis, sprint planning optimization, real-time dependency tracking.
Quality Insights: Dependency health metrics, coupling analysis, maintainability assessment, team workload distribution.
Output: Complete dependency analysis with visual representations, execution order recommendations, risk mitigation strategies, and optimization roadmap.