Menu
Use when running pre-commit, linting, type checking, or fixing CI failures in aiida-core.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | linting-and-ci |
| description | Use when running pre-commit, linting, type checking, or fixing CI failures in aiida-core. |
Always invoke via uv run so tools pick up the locked project environment.
Never use bare python or pip.
uv run pre-commit # check staged files
uv run pre-commit run --all-files # check everything
uv run pre-commit run mypy # run a specific hook
uv run pre-commit run ruff --all-files # run ruff on all files
uv run pre-commit run --from-ref main --to-ref HEAD # check only changes since branching off main
uv run pre-commit run --from-ref $(git merge-base main HEAD) --to-ref HEAD # same, but robust when main has advanced
Hooks worth knowing about: uv-lock (lockfile consistency), imports (auto-generates __all__), nbstripout, generate-conda-environment, verdi-autodocs.
CI enforces import-time constraints on src/aiida/cmdline/; see the adding-a-cli-command skill for details.
verdi shell # IPython shell with AiiDA loaded
verdi status # service status (daemon, storage, broker if configured)
verdi daemon start/stop/restart # manage the daemon
verdi devel check-load-time # check for import-time violations
Set AIIDA_WARN_v3=1 to surface deprecation warnings.
Use when adding a new `verdi` subcommand in `src/aiida/cmdline/`.
Use when adding a new third-party dependency to aiida-core's `pyproject.toml`.
Use when exploring the aiida-core codebase structure, looking for key files, or understanding how packages relate to each other.
Use when making commits, creating branches, or preparing pull requests for aiida-core.
Use when diagnosing failed, stuck, or misbehaving AiiDA processes or the daemon.
Use when deprecating a public Python API or `verdi` CLI command in aiida-core.