tr.cursorrules

[ademsmk]

Summary by CodeRabbit

• Documentation
  • Updated the Conventional Commit Messages specification to Turkish, providing all guidelines and examples in the translated language.

[coderabbitai]

Walkthrough

The file rules/git-conventional-commit-messages/.cursorrules was completely rewritten, replacing its original English content with a Turkish translation of the Conventional Commit Messages specification. The technical structure and information remain unchanged, with only the language of the documentation altered.

Changes

File(s)	Change Summary
rules/git-conventional-commit-messages/.cursorrules	Replaced English specification with a full Turkish translation; no changes to technical content or structure.

Poem

In burrows deep, a rule was spun,
Now written in Turkish, for everyone!
Same specs and structure, just a new tongue,
For every commit message, old and young.
The rabbit hops, translation complete—
Documentation now feels extra sweet! 🐇✨

---

🪧 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.

[Copilot]

Pull Request Overview

This PR replaces the English Conventional Commit Messages specification with a full Turkish translation in the .cursorrules file.

• Translated all commit message guidelines into Turkish
• Replaced English list items and specification details
• Updated keyword definitions and formatted structural markers

Comments suppressed due to low confidence (2)

rules/git-conventional-commit-messages/.cursorrules:1

• List items in this section should be prefixed with a '-' to match the bullet style used elsewhere in the file.

Konvansiyonel Taahhüt Mesajları spesifikasyonunu kullanarak taahhüt mesajları oluşturun

rules/git-conventional-commit-messages/.cursorrules:18

• The phrase 'BREAKING CHANGE:' is duplicated. Remove the extra prefix for clarity.

- BREAKING CHANGE: BREAKING CHANGE: altbilgisi olan veya ! ekleyen bir taahhüt tür/kapsamdan sonra, bir API değişikliğini (Anlamsal Sürümlemedeki MAJOR ile ilişkili) bozan bir API değişikliğini tanıtıyor. BREAKING CHANGE, herhangi bir türdeki commit'lerin bir parçası olabilir.

[coderabbitai]

Actionable comments posted: 0

🔭 Outside diff range comments (1)

rules/git-conventional-commit-messages/.cursorrules (1)

1-42: Configuration file overwritten with prose – build will break

.cursorrules is meant to contain Cursor rule definitions (machine-parsable JSON/YAML).
Replacing it with free-form Turkish documentation removes every rule, so any CI step or IDE integration that loads these rules will now fail (or silently stop linting commit messages).

Action items

1. Restore the original rule file (or recreate an equivalent Turkish-locale rule set in the expected format).
2. Move the translated spec to a Markdown file such as README_tr.md to keep both documentation and working configuration.

If the intention was only to provide docs, rename the file; keeping the .cursorrules extension is misleading and hazardous.

🧹 Nitpick comments (2)

rules/git-conventional-commit-messages/.cursorrules (2)

18-18: Duplicated phrase “BREAKING CHANGE: BREAKING CHANGE:”

The repetition looks accidental and makes the sentence hard to read.

- - BREAKING CHANGE: BREAKING CHANGE: altbilgisi olan …
+ - BREAKING CHANGE: altbilgisi olan …

---

25-25: Keyword list repeats “OLMALI”

In “ZORUNLU … OLMALI, OLMAMALI, OLMALI”, the second “OLMALI” is duplicated.

- "… OLMALI", "OLMAMALI", "OLMALI", "ÖNERİLEN" …
+ "… OLMALI", "OLMAMALI", "ÖNERİLEN" …

📜 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 c87d230.

📒 Files selected for processing (1)

• rules/git-conventional-commit-messages/.cursorrules (1 hunks)