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
Add tests for recently changed files or specified code
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?
System design and architecture planning mode. Focuses on high-level design, trade-offs, and technical decisions before implementation.
Explore the repository with 10 parallel subagents to create comprehensive documentation. Creates CODEBASE.md with full architecture analysis.
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.
Simplifies code after implementation. Reviews recent changes and suggests/applies simplifications while preserving behavior.
Create a conventional commit with auto-generated message
Commit staged changes, push to remote, and create a pull request