Files
wehub-resource-sync bb5c75ce05
Component Security Validation / Security Audit (push) Has been cancelled
Deploy to Cloudflare Pages / deploy (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:38:58 +08:00

1.8 KiB

Python Linter

Run Python code linting and formatting tools.

Purpose

This command helps you maintain code quality using Python's best linting and formatting tools.

Usage

/lint

What this command does

  1. Runs multiple linters (flake8, pylint, black, isort)
  2. Provides detailed feedback on code quality issues
  3. Auto-fixes formatting where possible
  4. Checks type hints if mypy is configured

Example Commands

Black (code formatting)

# Format all Python files
black .

# Check formatting without changing files
black --check .

# Format specific file
black src/main.py

flake8 (style guide enforcement)

# Check all Python files
flake8 .

# Check specific directory
flake8 src/

# Check with specific rules
flake8 --max-line-length=88 .

isort (import sorting)

# Sort imports in all files
isort .

# Check import sorting
isort --check-only .

# Sort imports in specific file
isort src/main.py

pylint (comprehensive linting)

# Run pylint on all files
pylint src/

# Run with specific score threshold
pylint --fail-under=8.0 src/

# Generate detailed report
pylint --output-format=html src/ > pylint_report.html

mypy (type checking)

# Check types in all files
mypy .

# Check specific module
mypy src/models.py

# Check with strict mode
mypy --strict src/

Configuration Files

Most projects benefit from configuration files:

.flake8

[flake8]
max-line-length = 88
exclude = .git,__pycache__,venv
ignore = E203,W503

pyproject.toml

[tool.black]
line-length = 88

[tool.isort]
profile = "black"

Best Practices

  • Run linters before committing code
  • Use consistent formatting across the project
  • Fix linting issues promptly
  • Configure linters to match your team's style
  • Use type hints for better code documentation