agentleFS
Sign inStart free
ludo-technologiesludo-technologies/python-best-practices/skills/tooling/SKILL.md

tooling

Skill34 starsChanged 4 months agoMITView on GitHub

Python development tooling configuration and best practices for ruff, mypy, pytest, pyscn, and uv. Use when setting up a Python project, configuring linters, formatters, type checkers, or test frameworks, or when editing pyproject.toml or tool config files.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. dotnet/efcore★ 15ksame name
    2. highcharts/highcharts★ 13ksame name
    3. alchemyplatform/aa-sdk★ 321same name
    4. TheBeardedBearSAS/claude-craft★ 108same name
    5. umararshad4/honey-stack★ 5same 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test framework configuration with pytest for reliable testing.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Python Tooling

A comprehensive guide to Python development tools. Configuration best practices for analysis, linters, type checkers, formatters, test frameworks, and package managers.

Why These Tools Matter

To write high-quality Python code, we recommend adopting these tools:

  • pyscn - Detect dead code, duplicates, and circular dependencies to prevent technical debt
  • ruff - Catch bugs and style violations early with fast static analysis
  • mypy - Find errors before runtime with type checking, also improves IDE completion
  • pytest - Build confidence in changes with reliable tests
  • uv - Improve developer experience with fast dependency management

Integrating these into CI/CD reduces code review burden and maintains consistent quality.

Categories

Analysis [HIGH]

Structural code analysis for quality assessment.

RuleDescription
analysis-pyscnDead code, clones, dependencies, complexity with pyscn

Linting [CRITICAL]

Static code analysis with ruff for consistent, high-quality code.

RuleDescription
lint-ruffFast, comprehensive linting with ruff

Type Checking [HIGH]

Static type checking with mypy for type safety and better IDE support.

RuleDescription
type-mypyStatic type checking with mypy

Formatting [HIGH]

Consistent code formatting with ruff format and import sorting.

RuleDescription
fmt-ruffCode formatting and import sorting with ruff

Testing [HIGH]

Test framework configuration with pytest for reliable testing.

RuleDescription
test-pytestTesting with pytest, fixtures, and coverage

Package Management [MEDIUM]

Modern Python packaging with uv and pyproject.toml.

RuleDescription
pkg-uvFast package management with uv
pkg-pyprojectProject configuration with pyproject.toml

Quick Reference

Minimal pyproject.toml

[project]
name = "myproject"
version = "0.1.0"
requires-python = ">=3.11"
dependencies = []

[project.optional-dependencies]
dev = ["ruff", "mypy", "pytest", "pytest-cov", "pyscn"]

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

[tool.ruff.lint]
select = ["E", "F", "W", "I", "UP", "B", "BLE", "SIM", "PTH", "S110", "S112"]

[tool.ruff.lint.flake8-bandit]
check-typed-exception = true

[tool.mypy]
python_version = "3.11"
strict = true

[tool.pytest.ini_options]
testpaths = ["tests"]
addopts = ["-v", "--tb=short"]

[tool.pyscn]
max_complexity = 15

Common Commands

# Analysis
pyscn analyze .                 # Full quality analysis
pyscn check .                   # CI quality gate

# Linting
ruff check .                    # Check for issues
ruff check . --fix              # Auto-fix issues

# Formatting
ruff format .                   # Format code

# Type checking
mypy .                          # Type check

# Testing
pytest                          # Run tests
pytest --cov=src                # With coverage

# Package management (uv)
uv pip install -e ".[dev]"      # Install with dev deps
uv pip compile pyproject.toml -o requirements.lock

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free