Enable pre-commit.ci and configure mypy (#61)

* Enable pre-commit.ci and skip mypy

Applies the same pre-commit.ci config as for `movement`.

I've also enabled the pre-commit.ci app in GitHub settings.

* Add pandas-stubs and xarray to mypy pre-commit deps

poseinterface imports pandas and xarray directly, so the mypy hook
needs their type stubs to perform real type checking (mirrors the
typed deps added in movement#721).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* mention pre-commit.ci in contributing guide

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: niksirbi

.pre-commit-config.yaml

@@ -3,6 +3,7 @@ exclude: 'conf.py'
 # Configuring https://pre-commit.ci/
 ci:
     autoupdate_schedule: monthly
+    skip: [mypy] # Build exceeds tier max size 250MiB
 
 repos:
     - repo: https://github.com/pre-commit/pre-commit-hooks
@@ -29,7 +30,9 @@ repos:
       hooks:
           - id: mypy
             additional_dependencies:
+                - pandas-stubs
                 - types-setuptools
+                - xarray
     - repo: https://github.com/mgedmin/check-manifest
       rev: "0.50"
       hooks:

docs/source/contributing.md

@@ -44,6 +44,12 @@ git add .
 pre-commit run
 ```
 
+These hooks also run automatically on every pull request via
+[pre-commit.ci](https://pre-commit.ci/) (except `mypy`, which is skipped there
+but still runs locally and in the test workflow). If a hook auto-fixes
+something, the bot will push the fix to your branch, so remember to pull before
+continuing to work.
+
 If a problem cannot be auto-fixed, the corresponding tool will provide
 information on what the issue is and how to fix it. For example, `ruff` might
 output something like: