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.6 KiB
1.6 KiB
allowed-tools: Read, Bash, Grep, Glob
argument-hint: [scope] | --api-keys | --passwords | --certificates | --fix
description: Scan codebase for exposed secrets, credentials, and sensitive information
Secrets Scanner
Scan codebase for exposed secrets and sensitive information: $ARGUMENTS
Current Repository State
- Git status: !
git status --porcelain | wc -luncommitted files - File types: !
find . -name "*.js" -o -name "*.py" -o -name "*.env*" -o -name "*.yml" | wc -lscannables - Recent commits: !
git log --oneline --grep="password\|key\|secret\|token" -5 - Environment files: @.env* or @config/* (if exists)
Task
Perform comprehensive secrets detection and remediation across codebase:
Scan Scope: Use $ARGUMENTS to focus on API keys, passwords, certificates, or complete scan
Detection Categories:
- API Keys & Tokens - GitHub, AWS, Google Cloud, Stripe, third-party services
- Database Credentials - Connection strings, usernames, passwords
- Certificates & Keys - Private keys, SSH keys, SSL certificates
- Authentication Secrets - JWT secrets, session keys, OAuth credentials
- Configuration Leaks - Hardcoded URLs, internal endpoints, debug settings
Remediation Actions:
- Identify exposed secrets with file locations and line numbers
- Provide secure alternatives (environment variables, secret management)
- Generate .gitignore entries for sensitive files
- Create secure configuration templates
- Implement secrets management best practices
Output: Detailed security report with risk levels, immediate actions, and long-term security improvements.