issue: 4480494 Add Cursor rules for dev workflow #514
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomerdbz
requested review from
AlexanderGrissik,
BasharRadya,
OmriRitblat and
pasis
Greptile Summary
Confidence Score: 3/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Developer
participant CursorAI as "Cursor AI"
participant Git
participant Redmine as "Redmine MCP"
Note over Developer,Redmine: Bug Investigation Workflow
Developer->>CursorAI: "@evaluate-bug.mdc [ticket#]"
CursorAI->>Redmine: "yai__get_tickets(ticket_id)"
Redmine-->>CursorAI: "Ticket details"
CursorAI->>Redmine: "yai__get_comments(ticket_id)"
Redmine-->>CursorAI: "Comments and discussion"
CursorAI->>Redmine: "yai__get_similar_issues(ticket_id)"
Redmine-->>CursorAI: "Related issues"
CursorAI->>Git: "Search codebase for affected code"
Git-->>CursorAI: "Code locations and history"
CursorAI-->>Developer: "Root cause analysis with diagrams"
Note over Developer,Redmine: Commit Message Workflow
Developer->>Git: "git add [files]"
Developer->>CursorAI: "@commit-msg.mdc"
CursorAI->>Git: "git diff --staged"
Git-->>CursorAI: "Staged changes"
CursorAI->>Git: "git config user.name/email"
Git-->>CursorAI: "User details"
CursorAI->>Git: "Check branch name for issue ID"
Git-->>CursorAI: "Branch info"
CursorAI-->>Developer: "Formatted commit message"
Developer->>Git: "git commit -m [message]"
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| ## Next Steps | ||
|
|
||
| After completing this evaluation: | ||
| - **If fix is needed**: Use `@solve-bug.mdc [ticket#]` to generate solution proposals |
There was a problem hiding this comment.
logic: References @solve-bug.mdc which doesn't exist in this PR or repository. Either include this file or update the reference to reflect the actual workflow.
Comment on lines
+29
to
+35
| - **Maximum length**: 51 characters (for optimal git log display) | ||
| - **Style**: Use imperative mood (e.g., "Add feature" not "Added feature") | ||
| - **Content**: Brief, actionable description of the change | ||
| - **Example**: `issue: 12345 Fix memory leak in buffer pool` | ||
|
|
||
| ### Body | ||
| - **Line length**: Maximum 72 characters per line (for readability in various git tools) |
There was a problem hiding this comment.
style: Line length limits (51 chars for subject, 72 for body) conflict with docs/contributing.md:116 which specifies 100 characters maximum for all lines. Consider aligning with project guidelines or updating the contributing docs.
Comment on lines
+16
to
+22
| 1. Fetch the full ticket using `yai__get_tickets` with ticket ID | ||
| 2. Extract key information: | ||
| - Bug description and reproduction steps | ||
| - Affected versions, components, priority | ||
| - Attachments (logs, screenshots, stack traces) | ||
| 3. Review comments using `yai__get_comments` | ||
| 4. Search for similar issues using `yai__get_similar_issues` |
There was a problem hiding this comment.
style: References Redmine MCP tools (yai__get_tickets, yai__get_comments, yai__get_similar_issues) without setup verification. This rule will fail if the Redmine MCP server isn't configured. Add prerequisite check or document setup requirements.
Add two Cursor AI rules to streamline development workflow: - commit-msg.mdc: Automates generation of well-formatted commit messages following project conventions with proper Redmine issue tracking and sign-off requirements - evaluate-bug.mdc: Provides structured approach for bug investigation using Redmine MCP integration, including ticket analysis, codebase investigation, and root cause analysis with visual diagrams These rules enable AI-assisted development by encoding project best practices and integrating with existing tools. Signed-off-by: Tomer Cabouly <[email protected]>
tomerdbz
force-pushed
the
4480494_cursor_rules_pilot
branch
from
5625a34 to
c13a4aa
Compare
There was a problem hiding this comment.
2 files reviewed, no comments
Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add two Cursor AI rules to streamline development workflow:
commit-msg.mdc: Automates generation of well-formatted commit messages following project conventions with proper Redmine issue tracking and sign-off requirements
evaluate-bug.mdc: Provides structured approach for bug investigation using Redmine MCP integration, including ticket analysis, codebase investigation, and root cause analysis with visual diagrams
These rules enable AI-assisted development by encoding project best practices and integrating with existing tools.
What
Streamline workflows with A.I. using rules.
Why ?
Justification for the PR. If there is existing issue/bug please reference.
How ?
It is optional but for complex PRs please provide information about the design,
architecture, approach, etc.
Change type
What kind of change does this PR introduce?
Check list