Skip to content

feat: add Scala general cursorrules and with Kafka usage, closes #83#130

Merged
PatrickJS merged 3 commits intoPatrickJS:mainfrom
seyfer:feat/add-scala-cursor-rules
Jul 24, 2025
Merged

feat: add Scala general cursorrules and with Kafka usage, closes #83#130
PatrickJS merged 3 commits intoPatrickJS:mainfrom
seyfer:feat/add-scala-cursor-rules

Conversation

@seyfer
Copy link
Contributor

@seyfer seyfer commented Jul 22, 2025

This is a proposal for general Scala cursor rules with Kafka usage.
These have already been tested for a few months at my main workplace.

Summary by CodeRabbit

  • Documentation

    • Added a comprehensive Scala 3 development best practices guide, including coding standards for Kafka Streams projects.
    • Introduced clean code guidelines for Scala, covering variable naming, immutability, and code complexity.
    • Added linting and formatting rules enforcing a Google-inspired scalafmt configuration with a 100-column line length.
    • Added Kafka development best practices for Scala projects, including topic configuration, serialization, and testing guidelines.
  • Chores

    • Added a .gitignore entry to exclude the .idea directory from version control.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

"""

Walkthrough

This update introduces a .gitignore file to exclude JetBrains IDE settings and adds four new markdown rule files defining comprehensive Scala coding standards, clean code guidelines, Kafka development best practices, and linting/formatting rules for a Kafka Streams project.

Changes

File(s) Change Summary
.gitignore Added to ignore .idea directory (JetBrains IDE settings).
rules/scala-kafka-cursorrules-prompt-file/general-scala-clean-code.mdc New rules file with Scala clean code guidelines (variable scope, naming, for-comprehension depth, immutability).
rules/scala-kafka-cursorrules-prompt-file/general-scala-development-practices.mdc New detailed Scala 3 coding standards and best practices for Kafka Streams projects.
rules/scala-kafka-cursorrules-prompt-file/linting-formatting.mdc New linting/formatting rule enforcing Google-inspired scalafmt with 100-column line limit.
rules/scala-kafka-cursorrules-prompt-file/kafka-development-practices.mdc New Kafka-specific development best practices for Scala projects (topic config, serialization, testing).

Estimated code review effort

2 (~20 minutes)

Poem

In the warren where Scala streams flow,
New rules and clean code now brightly glow.
With .idea ignored, and scalafmt in line,
Kafka hops smoothly—oh, how divine!
🐇✨ Let’s write with care, and code with glee,
For in tidy burrows, the best bugs flee!
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9588bfe and 29dc1d5.

📒 Files selected for processing (3)
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-clean-code.mdc (1 hunks)
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-development-practices.mdc (1 hunks)
  • rules/scala-kafka-cursorrules-prompt-file/kafka-development-practices.mdc (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • rules/scala-kafka-cursorrules-prompt-file/kafka-development-practices.mdc
🚧 Files skipped from review as they are similar to previous changes (2)
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-clean-code.mdc
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-development-practices.mdc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Nitpick comments (1)
.gitignore (1)

1-2: Add common Scala / sbt artefacts to .gitignore.

Only ignoring .idea will still leave generated build artefacts and Metals/BSP files under version control. At minimum add:

 .idea
+target/
+.bsp/
+.metals/
+.project
+.classpath

This keeps the VCS clean for anyone using the usual Scala tooling.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42ac7cf and 61c698b.

📒 Files selected for processing (4)
  • .gitignore (1 hunks)
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-clean-code.mdc (1 hunks)
  • rules/scala-kafka-cursorrules-prompt-file/general-scala-development-practices.mdc (1 hunks)
  • rules/scala-kafka-cursorrules-prompt-file/linting-formatting.mdc (1 hunks)

@seyfer
Copy link
Contributor Author

seyfer commented Jul 22, 2025

to be reviewed by @PatrickJS

@PatrickJS PatrickJS merged commit f80f73c into PatrickJS:main Jul 24, 2025
1 check passed
@seyfer seyfer deleted the feat/add-scala-cursor-rules branch July 24, 2025 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants