Files
davila7__claude-code-templates/cli-tool/components/commands/database/supabase-security-audit.md
Dani 054c0e56e9 fix(commands): Remove deprecated 'model: sonnet' field from 142 command files
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>
2025-10-21 10:08:58 -04:00

2.3 KiB

allowed-tools: Read, Write, Edit, Bash argument-hint: [audit-scope] | --rls | --permissions | --auth | --api-keys | --comprehensive description: Conduct comprehensive Supabase security audit with RLS analysis and vulnerability assessment

Supabase Security Audit

Conduct comprehensive Supabase security audit with RLS policy analysis and vulnerability assessment: $ARGUMENTS

Current Security Context

  • Supabase access: MCP integration for security analysis and policy review
  • RLS policies: Current Row Level Security implementation and policy effectiveness
  • Auth configuration: !find . -name "*auth*" -o -name "*supabase*" | grep -E "\\.(js|ts|json)$" | head -5 authentication setup
  • API security: Current API key management and access control implementation

Task

Execute comprehensive security audit with vulnerability assessment and policy optimization:

Audit Scope: Use $ARGUMENTS to focus on RLS policies, permission analysis, authentication security, API key management, or comprehensive security review

Security Audit Framework:

  1. RLS Policy Analysis - Review Row Level Security policies, test policy effectiveness, identify policy gaps, optimize policy performance
  2. Permission Assessment - Analyze table permissions, review role-based access, validate permission hierarchies, identify over-privileged access
  3. Authentication Security - Review auth configuration, analyze JWT security, validate session management, assess multi-factor authentication
  4. API Key Management - Audit API key usage, review key rotation policies, validate key scoping, assess exposure risks
  5. Data Protection - Analyze sensitive data handling, review encryption implementation, validate data masking, assess backup security
  6. Vulnerability Scanning - Identify security vulnerabilities, assess injection risks, review CORS configuration, validate rate limiting

Advanced Features: Automated security testing, policy simulation, vulnerability scoring, compliance checking, security monitoring setup.

Compliance Integration: GDPR compliance checking, SOC2 requirements validation, security best practices enforcement, audit trail analysis.

Output: Comprehensive security audit report with vulnerability assessments, policy recommendations, security improvements, and compliance validation.