python-toolkit

This skill should be used when the user asks to "configure the python project", "set up ruff", "configure pyright", "scaffold a pixi project", "add a ruff config", or otherwise requests scaffolding or modification of ruff/pyright/pixi configuration files. Detects existing configs and creates or updates them with sensible defaults, prompting before overwriting.

This skill should be used when the user asks to "review diagnostics", "check code quality", "show lint violations", "explain this error", or when ruff/ty diagnostic output appears in a tool result without an explicit user request. Provides structured diagnostic triage with severity bucketing, AST-scoped fix suggestions, and noise-suppression integration for the python-toolkit's ruff and ty passes.

This skill should be used when the user asks to "show project info", "what python tools are installed", "detect the project type", "summarize the toolchain", "show pixi info", or otherwise requests an overview of the current python project and its tool availability. Reports project type, Python version, config files, and tool versions (probes both ty and pyright).

Use when you see ruff violations, '[*] fixable with --fix', ty/pyright diagnostics, or Python import errors in terminal output. Also use when the user asks about lint rules, type errors, code stats, or project configuration.

This skill should be used when the user asks to "explain a ruff rule", "what does F401 mean", "show me rule E501", "explain this lint code", or otherwise requests the definition or rationale for a specific ruff rule code. Wraps `ruff rule <code>` with optional discovery via `ruff check --statistics .` when no code is given.

ty

ruff