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