lint-fix
The lint-fix slash command automatically detects a project's programming language and applies format and lint corrections using the appropriate tools for that environment, such as eslint, Prettier, Black, ruff, gofmt, and cargo fmt. Use this command when you need to quickly resolve formatting inconsistencies and auto-fixable linting violations across staged or recent changes in a codebase.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/lint-fix.md -o ~/.claude/commands/lint-fix.mdlint-fix.md
## Context - Project type: !`ls package.json 2>/dev/null && echo "node" || ls pyproject.toml setup.py requirements.txt 2>/dev/null && echo "python" || ls go.mod 2>/dev/null && echo "go" || ls Cargo.toml 2>/dev/null && echo "rust" || echo "unknown"` - Lint config files: !`ls .eslintrc* .prettierrc* eslint.config.* pyproject.toml .flake8 .golangci.yml rustfmt.toml 2>/dev/null || echo "No lint config found"` - Package scripts: !`cat package.json 2>/dev/null | grep -A 20 '"scripts"' | head -25 || echo "No package.json"` - Files to lint: !`git diff --name-only --cached 2>/dev/null || git diff --name-only HEAD~1 2>/dev/null || echo "all files"` ## Task Auto-fix all linting and formatting issues: 1. Detect the project type and available linters 2. Run formatters first (Prettier, Black, gofmt, rustfmt) 3. Run linters with auto-fix enabled: - JavaScript/TypeScript: `eslint --fix` - Python: `ruff check --fix` or `black` + `isort` - Go: `gofmt -w` + `go vet` - Rust: `cargo fmt` + `cargo clippy --fix` 4. Report what was fixed 5. List any remaining issues that require manual attention Scope: $ARGUMENTS
Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, when asked to review changes, PR review, code quality check, lint, or standards audit. Focuses on quality, security, performance, and maintainability.
Expert debugging specialist for errors, test failures, crashes, segmentation faults, memory leaks, timeouts, race conditions, deadlocks, and unexpected behavior. Use PROACTIVELY when encountering any error, exception, or failing test. Performs systematic root cause analysis.
Technical documentation specialist. Use for creating README files, API documentation, architecture docs, inline comments, user guides, changelogs, migration guides, release notes, FAQs, and troubleshooting docs. MUST BE USED when documentation is needed or when code changes require doc updates.
Master coordinator for complex multi-step tasks. Use PROACTIVELY when a task involves 2+ modules, requires delegation to specialists, needs architectural planning, or involves GitHub PR workflows. MUST BE USED for open-ended requests like "improve", "enhance", "build", "scale", "refactor", "add feature", "system design", "architecture", "complex task", or when implementing features from GitHub issues.
Code refactoring specialist for improving code quality, reducing technical debt, eliminating code smells, reducing complexity, and applying design patterns. Use PROACTIVELY when code needs restructuring, simplification, tech debt reduction, or when applying DRY/SOLID principles.
Security specialist for vulnerability detection, secure coding review, and security hardening. Use PROACTIVELY when handling authentication, authorization, encryption, secrets, credentials, OAuth, JWT, CORS, headers, user input, API keys, or sensitive data. Checks for OWASP Top 10 and common vulnerabilities.
Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use PROACTIVELY when adding new features, fixing bugs, improving test coverage, creating test plans, mocking strategies, handling flaky tests, or writing integration/E2E tests.
Add tests for recently changed files or specified code