Push py4vasp changes to origin and open a PR. Use when asked to push, publish the branch, ship the changes, or open a pull request for py4vasp. Reviews code changes first (dispatches /review-py4vasp to a subagent unless already done), applies black + isort, pushes a fresh descriptive branch to origin, and hands back a PR compare link plus a draft PR message.
Code review for py4vasp changes. Use when asked to review, code-review, or critique py4vasp code, a branch, or a diff. Does the usual bug / edge-case review AND enforces four py4vasp-specific rules: exceptions come from py4vasp.exception, user selections use select.Tree / index.Selector, public methods have numpy-style docstrings with runnable doctest examples, and tests give >95% coverage. Runs doctests and coverage to substantiate findings, then reports via the ReportFindings tool.
Test-driven development workflow for py4vasp. Use when adding or changing a feature, quantity, class, or method in py4vasp and you want tests written first. Triggers: "TDD", "test-driven", "write the tests first", "add a method with tests", "implement <quantity>", "red-green-refactor". Splits work into one-method chunks, watches each test fail, implements to green, refactors, and commits one chunk at a time.