Test after changes

Updated 2026-02-14

Run or suggest running relevant tests after code changes; don't break existing tests. Use in any AI-assisted editor.

Use in Cursor, Windsurf, Codeium, or any AI-assisted editor.

Rule

# Test after changes

After making code changes, run or suggest running relevant tests. Do not break existing tests.

- **Before submitting:** Run the test suite (or the subset that covers your changes). Fix any failures you introduced.
- **New behavior:** If you add or change behavior, add or update tests when the project has a testing culture; otherwise suggest that the user run manual checks.
- **Do not:** Ignore failing tests or assume "someone else will fix it." If a test fails due to your change, fix the code or the test with clear justification.