configure

Configure

Purpose

Configure python development tools — ruff (lint/format), pyright (type-check), and pixi (project manager). Scaffold configuration files with sensible defaults when none exist; show the current state and ask before overwriting when they do.

Procedure

1. Parse the user's request for a tool selector (ruff, pyright, pixi, or all). If no selector is provided, detect existing configs and present a menu so the user can choose.

2. Detection phase — check for existing config files in the current directory:

   • ruff.toml or [tool.ruff] section in pyproject.toml
   • pyrightconfig.json or [tool.pyright] section in pyproject.toml
   • pixi.toml
   • pyproject.toml (note which tool sections exist)

   Report what is present and what is missing.

3. If no selector was provided, present the detection results to the user and ask which tool to configure. Offer all to scaffold everything.

Configure ruff

4. If pyproject.toml exists, prefer adding a [tool.ruff] section there. Otherwise create a standalone ruff.toml.

5. Use these sensible defaults:

   # ruff.toml (or [tool.ruff] in pyproject.toml)
   line-length = 88
   target-version = "py312"
   
   [lint]
   select = ["E", "F", "I", "UP", "B"]
   

6. If a ruff config already exists, show the current settings and ask before overwriting.

Configure pyright

4. Create pyrightconfig.json with sensible defaults:

   {
       "typeCheckingMode": "standard",
       "pythonVersion": "3.12",
       "reportMissingImports": true,
       "reportMissingTypeStubs": false
   }
   

5. If pixi.toml is present, add "venvPath": "." and "venv": ".pixi/envs/default" to the pyright config.

6. If .venv/ is present, add "venvPath": "." and "venv": ".venv" to the pyright config.

7. If a pyright config already exists, show current settings and ask before overwriting.

Configure pixi

4. If pixi.toml does not exist, scaffold a minimal one (substitute the actual directory name for <directory-name>):

   [project]
   name = "<directory-name>"
   version = "0.1.0"
   channels = ["conda-forge"]
   platforms = ["linux-64", "win-64", "osx-arm64"]
   
   [dependencies]
   python = ">=3.12"
   

5. If pixi.toml already exists, show the current config and offer to add common features (dev dependencies, tasks, etc.).

Configure all

4. Run all three configurations in sequence (ruff → pyright → pixi), respecting existing configs (prompt before any overwrite).

5. Summarize what was created and what was modified.

Composition

This skill currently inlines its procedure (direct file detection + scaffolding). The forward-looking design per the v3 toolkit spec and the Path B decision is for this skill to invoke the shared diagnostic-review pipeline via:

Skill(skill: "python-toolkit:diagnostic-review", pass: "configure")

The shared diagnostic-review skill already ships at skills/diagnostic-review/SKILL.md and documents the pass: configure selector (auto-detects the project tier, diffs proposed updates against .toolkit.local.md, and prompts per-section). The per-pass invocation wiring lands in a separate chore — until then, this skill body matches the legacy /configure command behavior.