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
argument-hint: [scope] | --security | --licenses | --updates | --all
description: Audit dependencies for security vulnerabilities, license compliance, and update recommendations
Dependency Audit
Audit dependencies for security vulnerabilities and compliance: $ARGUMENTS
Current Dependencies
- Package files: @package.json or @requirements.txt or @Cargo.toml or @pom.xml
- Lock files: @package-lock.json or @poetry.lock or @Cargo.lock
- Security scan: !
npm audit --audit-level=moderate 2>/dev/null || pip check 2>/dev/null || cargo audit 2>/dev/null || echo "No security scanner available" - Outdated packages: !
npm outdated 2>/dev/null || pip list --outdated 2>/dev/null || echo "Check manually"
Task
Perform comprehensive dependency security and compliance audit:
Audit Scope: Use $ARGUMENTS to focus on security, licenses, updates, or complete audit
Analysis Areas:
- Vulnerability Scanning - Known CVEs, security advisories, exploit availability
- Version Analysis - Outdated packages, breaking changes, update recommendations
- License Compliance - License compatibility, restrictions, legal obligations
- Supply Chain Security - Package authenticity, maintainer status, suspicious dependencies
- Performance Impact - Bundle size, unused dependencies, optimization opportunities
Output: Prioritized security report with critical vulnerabilities, recommended actions, and compliance status.