info

Info

Purpose

Detect and report the state of the current python project: project type (pixi, pip+venv, setuptools, or unknown), Python version, available tooling (pixi, ruff, pyright), discovered config files, and missing recommended tools.

Procedure

1. Detect project type by checking for these files in the current working directory:

   • pixi.toml → pixi project
   • pyproject.toml → PEP 621 project
   • setup.cfg / setup.py → legacy setuptools
   • requirements.txt → pip requirements
   • .venv/ / venv/ → virtual environment present

2. Check tool availability by running:

   python --version 2>&1
   pixi --version 2>&1
   ruff --version 2>&1
   pyright --version 2>&1
   

3. Report a project overview covering:

   • Project type (pixi / pip+venv / setuptools / unknown)
   • Python version
   • Available tools (pixi, ruff, pyright) with versions
   • Config files found (pixi.toml, pyproject.toml, ruff.toml, pyrightconfig.json, etc.)
   • Missing recommended tools (advise installation when relevant)

4. If the project is a pixi project, surface pixi's own diagnostics:

   pixi info 2>&1
   

5. If the project is a pip-managed project with a virtual environment, surface the installed package count:

   pip list --format=columns 2>&1 | tail -n +3 | wc -l
   

6. Present a summary table of the project state.

Composition

This skill currently inlines its procedure (direct CLI detection + tool-version probes). The forward-looking design per the v3 toolkit spec and the Path B decision is for the shared diagnostic-review pipeline to provide a project-tier classifier (configured / partial / unconfigured) that this skill consumes. The invocation form will be:

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

The shared diagnostic-review skill ships at skills/diagnostic-review/SKILL.md. Per Path B this is forward-looking — the per-pass invocation wiring lands in a separate chore. Until then, this skill body matches the legacy /info command behavior.