Expert knowledge for using ruff check as an extremely fast Python linter with comprehensive rule support and automatic fixing.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionruff-lintingExecute the skills CLI command in your project's root directory to begin installation:
Fetches ruff-linting from laurigates/claude-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ruff-linting. Access via /ruff-linting in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23
stars
Expert knowledge for using ruff check as an extremely fast Python linter with comprehensive rule support and automatic fixing.
ruff Advantages
# Lint current directory
ruff check
# Lint specific files or directories
ruff check path/to/file.py
ruff check src/ tests/
# IMPORTANT: Pass directory as parameter to stay in repo root
# ✅ Good
ruff check services/orchestrator
# ❌ Bad
cd services/orchestrator && ruff check
# Show what would be fixed (diff preview)
ruff check --diff
# Apply safe automatic fixes
ruff check --fix
# Fix specific files
ruff check --fix src/main.py
# Fix with preview (see changes before applying)
ruff check --diff services/orchestrator
ruff check --fix services/orchestrator
# Default output
ruff check
# Show statistics
ruff check --statistics
# JSON output for tooling
ruff check --output-format json
# GitHub Actions annotations
ruff check --output-format github
# GitLab Code Quality report
ruff check --output-format gitlab
# Concise output
ruff check --output-format concise
| Code | Description | Example Rules |
|---|---|---|
E |
pycodestyle errors | E501 (line too long) |
F |
Pyflakes | F401 (unused import) |
W |
pycodestyle warnings | W605 (invalid escape) |
B |
flake8-bugbear | B006 (mutable default) |
I |
isort | I001 (unsorted imports) |
UP |
pyupgrade | UP006 (deprecated types) |
SIM |
flake8-simplify | SIM102 (nested if) |
D |
pydocstyle | D100 (missing docstring) |
N |
pep8-naming | N806 (variable naming) |
S |
flake8-bandit (security) | S101 (assert usage) |
C4 |
flake8-comprehensions | C400 (unnecessary generator) |
# Select specific rules at runtime
ruff check --select E,F,B,I
# Extend default selection
ruff check --extend-select UP,SIM
# Ignore specific rules
ruff check --ignore E501,E402
# Show which rules would apply
ruff rule --all
# Explain a specific rule
ruff rule F401
# List all available rules
ruff rule --all
# Search for rules by pattern
ruff rule --all | grep "import"
# Get detailed rule explanation
ruff rule F401
# Output: unused-import (F401)
# Derived from the Pyflakes linter.
# Checks for unused imports.
# List all linters
ruff linter
# JSON output for automation
ruff rule F401 --output-format json
[tool.ruff]
# Line length limit (same as Black)
line-length = 88
# Target Python version
target-version = "py311"
# Exclude directories
exclude = [
".git",
".venv",
"__pycache__",
"build",
"dist",
]
[tool.ruff.lint]
# Enable specific rule sets
select = [
"E", # pycodestyle errors
"F", # Pyflakes
"B", # flake8-bugbear
"I", # isort
"UP", # pyupgrade
"SIM", # flake8-simplify
]
# Disable specific rules
ignore = [
"E501", # Line too long (handled by formatter)
"B008", # Function calls in argument defaults
]
# Allow automatic fixes
fixable = ["ALL"]
unfixable = ["B"] # Don't auto-fix bugbear rules
# Per-file ignores
[tool.ruff.lint.per-file-ignores]
"__init__.py" = ["F401", "E402"]
"tests/**/*.py" = ["S101"] # Allow assert in tests
# Same options as pyproject.toml but without [tool.ruff] prefix
line-length = 100
target-version = "py39"
[lint]
select = ["E", "F", "B"]
ignore = ["E501"]
[lint.isort]
known-first-party = ["myapp"]
force-single-line = true
# Override settings for specific paths
ruff check --config path/to/ruff.toml
# Use inline configuration
ruff check --select E,F,B --ignore E501
# Check only specific rule codes
ruff check --select F401,F841 # Only unused imports/variables
# Security-focused check
ruff check --select S # All bandit rules
# Import organization only
ruff check --select I --fix
# Docstring checks
ruff check --select D
# Check only changed files (git)
git diff --name-only --diff-filter=d | grep '\.py$' | xargs ruff check
# Check files modified in branch
git diff --name-only main...HEAD | grep '\.py$' | xargs ruff check
# Parallel checking of multiple directories
ruff check src/ &
ruff check tests/ &
wait
# Combine with other tools
ruff check && pytest && ty check
# .pre-commit-config.yaml
repos:
- repo: https://github.com/astral-sh/ruff-pre-commit
rev: v0.14.0
hooks:
# Linter with auto-fix
- id: ruff-check
args: [--fix]
# Advanced configuration
- id: ruff-check
name: Ruff linter
args:
- --fix
- --config=pyproject.toml
- --select=E,F,B,I
types_or: [python, pyi, jupyter]
# .github/workflows/lint.yml
name: Lint
on: [push, pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/ruff-action@v3
with:
args: 'check --output-format github'Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ruff-linting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
ruff-linting is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
ruff-linting reduced setup friction for our internal harness; good balance of opinion and flexibility.
ruff-linting has been reliable in day-to-day use. Documentation quality is above average for community skills.
ruff-linting reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added ruff-linting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: ruff-linting is the kind of skill you can hand to a new teammate without a long onboarding doc.
ruff-linting has been reliable in day-to-day use. Documentation quality is above average for community skills.
ruff-linting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added ruff-linting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 36