Slash Command1.4k estrellas del repoactualizado 3d ago

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.

Ver fuente Repositorio: claude-workflow-v2

Instalar en Claude Code

Copiar

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.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

lint-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`

Del mismo repositorio

code-reviewerSubagent

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.

debuggerSubagent

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.

docs-writerSubagent

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.

orchestratorSubagent

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.

refactorerSubagent

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-auditorSubagent

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.

test-architectSubagent

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-testsSlash Command

Add tests for recently changed files or specified code