ruff
Skill1 starsChanged 8 months agoMITView on GitHub
Ruff is an extremely fast Python linter and code formatter. It replaces Flake8, isort, Black, pyupgrade, autoflake, and dozens of other tools. Always use ruff for Python linting and formatting, especially if you see: However, avoid making unnecessary changes: - Don't format unformatted code - If ruff format --diff shows changes throughout an entire file, the project likely isn't using ruff for formatting. Skip formatting to avoid obscuring actual changes. - Scope fixes to code being edited - Use ruff…
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Nox-Lumen-tech/combo-skillstheir own version, first seen Nov 2, 2026
- Egoushka/agent-skillsword for word, first seen Oct 13, 2026
- moabualruz/fulcrumtheir own version, first seen Apr 28, 2026
- astral-sh/claude-code-pluginsword for word, first seen Feb 27, 2026
Other versions5 projects use a version of this.
Word for word · 3
- astral-sh/claude-code-plugins★ 311100% same
- aaaxn/skills★ 2100% same
- Egoushka/agent-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- moabualruz/fulcrum★ 4same name
- Nox-Lumen-tech/combo-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architect-reviewSkill
- brainstormingSkill
- changelog-writerSkill
- dispatching-parallel-agentsSkill
- documentation-writerSkill
- executing-plansSkill
- fastapiSkill
- makefileSkill
- pgvector-semantic-searchSkill
- postgres-patternsSkill
- python-patternsSkill
- python-testingSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- task-doc-navigatorSkill
- test-driven-developmentSkill
- tySkill
- using-git-worktreesSkill
- using-superpowersSkill
- uvSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Don't format unformatted code: - If ruff format --diff shows changes throughout an entire file, the project likely isn't using ruff for …
- Very specific: line 25
Scope fixes to code being edited: - Use ruff check --diff to see fixes relevant to the code you're changing.
- Very specific: line 106
Run ruff check --fix before ruff format.
- Very specific: line 127
Use ruff rule <CODE> to understand why the fix is considered unsafe
- Distinctive: line 128
Verify the fix doesn't violate those assumptions in your code
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ruff
Ruff is an extremely fast Python linter and code formatter. It replaces Flake8, isort, Black, pyupgrade, autoflake, and dozens of other tools.
When to use ruff
Always use ruff for Python linting and formatting, especially if you see:
[tool.ruff]section inpyproject.toml- A
ruff.tomlor.ruff.tomlconfiguration file
However, avoid making unnecessary changes:
- Don't format unformatted code - If
ruff format --diffshows changes throughout an entire file, the project likely isn't using ruff for formatting. Skip formatting to avoid obscuring actual changes. - Scope fixes to code being edited - Use
ruff check --diffto see fixes relevant to the code you're changing. Only apply fixes to files you're modifying unless the user explicitly asks for broader fixes.
How to invoke ruff
uv run ruff ...- Use when ruff is in the project's dependencies to ensure you use the pinned versionuvx ruff ...- Use when ruff is not a project dependency, or for quick one-off checksruff ...- Use if ruff is installed globally
Commands
Linting
ruff check . # Check all files in current directory
ruff check path/to/file.py # Check specific file
ruff check --fix . # Auto-fix fixable violations
ruff check --fix --unsafe-fixes . # Include unsafe fixes (review changes!)
ruff check --watch . # Watch for changes and re-lint
ruff check --select E,F . # Only check specific rules
ruff check --ignore E501 . # Ignore specific rules
ruff rule E501 # Explain a specific rule
ruff linter # List available lintersFormatting
ruff format . # Format all files
ruff format path/to/file.py # Format specific file
ruff format --check . # Check if files are formatted (no changes)
ruff format --diff . # Show formatting diff without applyingConfiguration
Ruff is configured in pyproject.toml or ruff.toml:
# pyproject.toml
[tool.ruff.lint]
select = ["E", "F", "I", "UP"] # Enable specific rule sets
ignore = ["E501"] # Ignore specific rules
[tool.ruff.lint.isort]
known-first-party = ["myproject"]Migrating from other tools
Black → ruff format
black . → ruff format .
black --check . → ruff format --check .
black --diff . → ruff format --diff .Flake8 → ruff check
flake8 . → ruff check .
flake8 --select E,F . → ruff check --select E,F .
flake8 --ignore E501 . → ruff check --ignore E501 .isort → ruff check
isort . → ruff check --select I --fix .
isort --check . → ruff check --select I .
isort --diff . → ruff check --select I --diff .Common patterns
Apply lint fixes before formatting
Run ruff check --fix before ruff format. Lint fixes can change code
structure (e.g., reordering imports), which formatting then cleans up.
ruff check --fix .
ruff format .Applying and reviewing unsafe fixes
Ruff categorizes some auto-fixes as "unsafe" because they may change code behavior, not just style. For example, removing unused imports could break code that relies on side effects.
ruff check --fix --unsafe-fixes --diff . # Preview changes first
ruff check --fix --unsafe-fixes . # Apply changesAlways review changes before applying --unsafe-fixes:
- Use
ruff rule <CODE>to understand why the fix is considered unsafe - Verify the fix doesn't violate those assumptions in your code
Documentation
For detailed information, read the official documentation:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

