Skip to content

chore(cursor): Add Rust formatting check to Cursor rules #2696

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
HazAT wants to merge 1 commit into from
Closed

chore(cursor): Add Rust formatting check to Cursor rules #2696

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .cursor/rules/sentry-cli-project.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,4 +65,8 @@ Reference: https://develop.sentry.dev/engineering-practices/commit-messages/
- Test fixtures in `tests/integration/_fixtures/`
- Cross-platform testing via CI matrix

## Code Formatting

- Always run `cargo fmt --all -- --check` before committing to ensure consistent Rust code formatting
Copy link
Copy Markdown
Member

@szokeasaurusrex szokeasaurusrex Aug 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already run cargo fmt --all -- --check to verify correct formatting in CI, so there is no need for the LLM to verify it before committing.

However, running cargo fmt --all, which actually fixes formatting rather than just validating it, could in fact be useful:

Suggested change
- Always run `cargo fmt --all -- --check` before committing to ensure consistent Rust code formatting
- Always run `cargo fmt --all` before committing to ensure consistent Rust code formatting

I would also suggest placing this line in .cursor/rules/rust-development.mdc, as it is only relevant to Rust development.


Remember: This is a production tool used by many developers. Changes should be well-tested, backward-compatible, and follow established patterns.