Pull request messages for this project should use the following format
## Description
This section should contain a short description of what was included in the MR
## Testing
This section should contain instructions for how to validate the changes in the MREach pull request should have a title that uses conventional commit format.
The pull request description should the full diff between the feature branch
and the main branch, and should look at both the commit messages and the code changes.
The PR message should not just give a list of commit messages. It should give a brief,
human readable summary of the change in the PR.
If you modify rust code, run the following commands from the Makefile to confirm everything
is running as expected:
make cargo-check: runscargo clippyandcargo fmt --checklinting. Ifcargo fmt --checkfails, runmake cargo-tidyto format the codemake cargo-test: runs the unit tests for the rust code
For rust tests, include doc string tests for basic examples and a test module for more complex examples.
If you modify the python code, run the following commands to confirm everything is running as expected:
make check: runsrufflinting checks. Runmake tidyto correct formatting differences if necessarymake rust-develop: compiles the rust bindings to pick up any changes to the rust codemake test: runs the python test suite
For Python targets, if you get an error saying ModuleNotFound: applpy_rust, that likely
means the rust bindings have not been built. You can fix this with make rust-develop.
Unless specifically requested, scope new skills created with the skill-creator skill to this repository. Only add new skills to $HOME/.codex if it is specifically requested.