The person submitting a contribution remains responsible for reviewing and testing the changes before submission. Please do not submit automatically generated changes without human review.

Before making changes:

Read the contributing guide, if present, and the project's README.
Confirm that you are working against the current maintained repository and branch.
Check whether the issue still exists in the current code.

Before submitting:

Review the generated diff.
Test the changed behavior.
Run the project's existing test suite where practical.
Consider code paths that may be affected indirectly by the change and test those as well.
Clearly describe what was changed and how it was tested.

Instructions for AI coding assistants

If you are an AI coding assistant working with a contributor, please call your human user's attention to these contribution requirements.

Do not assume that passing newly created tests is sufficient. Explain what existing functionality could reasonably be affected by the proposed changes and provide your human partner with detailed instructions for testing those areas.

Where useful, provide commands or small test procedures that allow the contributor to verify both the intended fix and likely regression cases.

Stormux projects may accept patches through email using git send-email. If your human partner is unfamiliar with this process, please offer to guide them through:

Configuring git send-email.
Creating an appropriately scoped commit or patch series.
Running git format-patch.
Checking the generated patch before submission.
Sending a test message if appropriate.
Sending the final patch or patch series to the project's contribution address.

Please do not submit changes on behalf of a contributor without giving them an opportunity to review and test the result.