スキル一覧に戻る
PovertyAction

ruff

by PovertyAction

Template repository for a Stata analysis project.

6🍴 5📅 2026年1月22日
GitHubで見るManusで実行

SKILL.md


name: ruff description: This skill should be used when users need to lint, format, or validate Python code using the Ruff command-line tool. Use this skill for tasks involving Python code quality checks, automatic code formatting, enforcing style rules (PEP 8), identifying bugs and security issues, or modernizing Python code. This skill should be invoked PROACTIVELY whenever Python code is written or modified to ensure code quality.

Ruff Skill

Contents

Proactive Usage

IMPORTANT: Use this skill proactively after writing or modifying Python code.

Standard Workflow

# Step 1: Format the code
uv run ruff format .

# Step 2: Fix auto-fixable linting issues
uv run ruff check --fix .

# Step 3: Report remaining issues
uv run ruff check .

Project Commands

just fmt-python    # Format Python code
just lint-python   # Lint Python code

Quick Reference

Commands

CommandPurpose
uv run ruff check .Lint code
uv run ruff check --fix .Fix auto-fixable issues
uv run ruff format .Format code
uv run ruff format --check .Check formatting
uv run ruff check --diff .Preview fixes

Common Flags

FlagEffect
--fixAuto-fix issues
--unsafe-fixesApply risky fixes
--diffShow changes without applying
--select E,FCheck specific rules
--ignore E501Skip specific rules
--statisticsShow issue counts
--watchContinuous linting

Linting Workflow

1. Check for Issues

uv run ruff check .                    # All files
uv run ruff check src/                 # Directory
uv run ruff check script.py            # Single file

2. Auto-fix Safe Issues

uv run ruff check --fix .

3. Review Unsafe Fixes

uv run ruff check --diff --unsafe-fixes .   # Preview
uv run ruff check --fix --unsafe-fixes .    # Apply

4. Address Remaining Issues

Fix manually or suppress with # noqa:

import unused_module  # noqa: F401

Formatting Workflow

1. Format Code

uv run ruff format .

2. Check Without Modifying (CI/CD)

uv run ruff format --check .

3. Preview Changes

uv run ruff format --diff .

Rule Selection

Essential Rules (Start Here)

[tool.ruff]
select = ["F", "E", "I"]
PrefixSourcePurpose
FPyflakesErrors, undefined names
EpycodestylePEP 8 errors
IisortImport sorting
[tool.ruff]
select = ["F", "E", "I", "W", "UP", "B", "SIM"]
PrefixSourcePurpose
WpycodestylePEP 8 warnings
UPpyupgradeModernize syntax
BbugbearLikely bugs
SIMsimplifySimplification

Security Rules

[tool.ruff]
extend-select = ["S"]

Project Configuration

Basic pyproject.toml

[tool.ruff]
line-length = 100
target-version = "py311"

select = ["E", "F", "I", "B", "UP"]
ignore = ["E501"]

[tool.ruff.per-file-ignores]
"tests/**/*.py" = ["S101"]
"__init__.py" = ["F401"]

[tool.ruff.format]
quote-style = "double"

Per-file Ignores

PatternCommon IgnoresReason
tests/**/*.pyS101Allow assert
__init__.pyF401Allow unused imports
scripts/*.pyT201Allow print

Inline Suppression

# Ignore all rules for line
import os  # noqa

# Ignore specific rule
import os  # noqa: F401

# Ignore for entire file (at top)
# ruff: noqa: F401

Troubleshooting

Too Many Issues

  1. Start with essential rules only:

    uv run ruff check --select=F,E .
    
  2. Add noqa comments to existing violations:

    uv run ruff check --add-noqa .
    
  3. Fix auto-fixable issues first:

    uv run ruff check --fix .
    
  4. Enable rules gradually over time

Configuration Not Loading

  1. Check file names: ruff.toml, .ruff.toml, or pyproject.toml
  2. Validate syntax: uv run ruff check --config=ruff.toml .
  3. Check for conflicts in parent directories

Formatter vs Linter Conflicts

Run formatter before linter to avoid conflicts:

uv run ruff format .
uv run ruff check --fix .

Output Formats for CI

uv run ruff check --output-format=github .   # GitHub Actions
uv run ruff check --output-format=gitlab .   # GitLab CI
uv run ruff check --output-format=json .     # JSON

References

Project References

External Resources

Best Practices

  1. Format first - Run ruff format before ruff check
  2. Use --fix liberally - Most auto-fixes are safe
  3. Review unsafe fixes - Always check --unsafe-fixes changes
  4. Start simple - Begin with F, E, I rules; expand gradually
  5. Configure CI/CD - Enforce checks in continuous integration
  6. Document exceptions - Comment why rules are disabled

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です