lint-check
The lint-check command detects and runs appropriate linting tools for JavaScript/TypeScript, Python, Go, and Rust projects, then categorizes findings into critical issues requiring manual fixes, warnings to address, and auto-fixable style problems. Use this command to catch code quality violations and enforce project standards before code reaches continuous integration systems.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/lint-check.md -o ~/.claude/commands/lint-check.mdlint-check.md
# Lint Check Run linting and code quality checks. Catches issues before they reach CI. ## Phase 1: Detect Linting Tools Find project's linting configuration: ```bash # JavaScript/TypeScript ls .eslintrc* eslint.config.* .prettierrc* 2>/dev/null # Python ls pyproject.toml .flake8 .ruff.toml setup.cfg 2>/dev/null # Go ls .golangci.yml .golangci.yaml 2>/dev/null # Rust ls rustfmt.toml .rustfmt.toml clippy.toml 2>/dev/null ``` ## Phase 2: Run Linters ### JavaScript/TypeScript ```bash npx eslint . --ext .js,.ts,.tsx --format stylish npx prettier --check . ``` ### Python ```bash ruff check . # or fallback flake8 . black --check . mypy . ``` ### Go ```bash golangci-lint run gofmt -l . go vet ./... ``` ### Rust ```bash cargo clippy -- -D warnings cargo fmt --check ``` ## Phase 3: Categorize Issues ### Critical (Must Fix) - Security vulnerabilities - Undefined variables - Type errors - Potential null pointer issues - SQL injection patterns ### Warnings (Should Fix) - Unused variables/imports - Missing return types - Inconsistent naming - Complex expressions ### Style (Auto-fixable) - Formatting issues - Import ordering - Trailing whitespace - Line length ## Phase 4: Auto-Fix Option Offer to auto-fix style issues: ```bash # JavaScript/TypeScript npx eslint . --fix npx prettier --write . # Python ruff check . --fix black . isort . # Go gofmt -w . # Rust cargo fmt ``` ## Output Format ``` ## Lint Results: [PASS/FAIL/WARNINGS] ### Summary - Errors: X - Warnings: Y - Auto-fixable: Z ### Critical Issues (Must Fix) 1. **[Rule]** - `file:line` - Message: [linter message] - Fix: [how to fix] ### Warnings (Should Fix) 1. **[Rule]** - `file:line` - Message: [message] ### Auto-Fixed (if --fix was run) - [List of auto-fixed issues] ### Commands Used - [List all linting commands run] ### Recommendation [ ] Ready to commit [ ] Fix critical issues first [ ] Run auto-fix and review changes ``` ## Usage This command ships with the project-starter plugin. Invoke with: `/project-starter:lint-check`
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