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>
36 lines
1.9 KiB
Markdown
36 lines
1.9 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [language] | --javascript | --typescript | --python | --multi-language
|
|
description: Configure comprehensive code linting and quality analysis tools with automated enforcement
|
|
---
|
|
|
|
# Setup Code Linting
|
|
|
|
Configure comprehensive code linting and quality analysis: **$ARGUMENTS**
|
|
|
|
## Current Code Quality State
|
|
|
|
- Languages detected: !`find . -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.rs" | head -5`
|
|
- Existing linters: @.eslintrc.* or @pyproject.toml or @tslint.json
|
|
- Package manager: @package.json or @requirements.txt or @Cargo.toml
|
|
- Code quality tools: !`which eslint flake8 pylint mypy clippy 2>/dev/null | wc -l`
|
|
|
|
## Task
|
|
|
|
Setup comprehensive code linting system with quality analysis and automated enforcement:
|
|
|
|
**Language Focus**: Use $ARGUMENTS to configure JavaScript/TypeScript ESLint, Python linting, or multi-language quality analysis
|
|
|
|
**Linting Configuration**:
|
|
1. **Tool Installation** - ESLint, Flake8, Pylint, MyPy, Clippy, language-specific linters and plugins
|
|
2. **Rule Configuration** - Code style rules, error detection, best practices, security patterns, performance guidelines
|
|
3. **IDE Integration** - Real-time linting, error highlighting, quick fixes, workspace settings
|
|
4. **Quality Gates** - Pre-commit validation, CI/CD integration, pull request checks, quality metrics
|
|
5. **Custom Rules** - Project-specific patterns, architectural constraints, team conventions
|
|
6. **Performance** - Incremental linting, caching strategies, parallel execution, optimization
|
|
|
|
**Advanced Features**: Security linting, accessibility checks, performance analysis, dependency analysis, code complexity metrics.
|
|
|
|
**Team Standards**: Shared configurations, style guides, review guidelines, onboarding documentation.
|
|
|
|
**Output**: Complete linting system with automated quality gates, team standards enforcement, and comprehensive code analysis. |