issue: 4480494 Add Cursor rules for dev workflow

[tomerdbz]

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?

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Tests
• [ ] Other

Check list

• [ ] Code follows the style de facto guidelines of this project
• [ ] Comments have been inserted in hard to understand places
• [ ] Documentation has been updated (if necessary)
• [ ] Test has been added (if possible)

[greptile-apps[bot]]

Greptile Overview

Greptile Summary

Adds two Cursor AI rules (.mdc files) to automate development workflows: commit-msg.mdc for generating properly formatted commit messages with Redmine issue tracking, and evaluate-bug.mdc for structured bug investigation using Redmine MCP integration.

Key Changes:

• commit-msg.mdc: Encodes project commit conventions (issue ID format, sign-off requirements, line length guidelines)
• evaluate-bug.mdc: Provides systematic approach for bug analysis including ticket investigation, codebase exploration, and root cause analysis

Minor Issues:

• Line length specifications in commit-msg.mdc (51/72 chars) don't perfectly align with docs/contributing.md:116 (100 chars max), though both are valid git best practices
• Both rules appropriately document their prerequisites and error handling

Confidence Score: 5/5

• This PR is safe to merge with minimal risk - adds documentation/configuration files only
• These are non-executable configuration files that provide guidance to AI tooling. They don't affect runtime behavior, build process, or production code. The line length guideline differences are stylistic preferences rather than breaking changes. Previous review comments were already addressed.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
.cursor/rules/commit-msg.mdc	4/5	Adds Cursor AI rule for automating commit message generation following project conventions, with minor line length conflict with contributing.md
.cursor/rules/evaluate-bug.mdc	5/5	Adds Cursor AI rule for structured bug investigation with Redmine MCP integration, includes appropriate prerequisite checks

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Cursor as Cursor AI
    participant Git as Git Repository
    participant Redmine as Redmine MCP

    Note over Dev,Redmine: Commit Message Workflow (commit-msg.mdc)
    Dev->>Cursor: Request commit message generation
    Cursor->>Git: git diff --staged
    Git-->>Cursor: Staged changes
    Cursor->>Git: git config user.name/email
    Git-->>Cursor: User configuration
    Cursor->>Cursor: Generate formatted message<br/>(issue ID + title + body + sign-off)
    Cursor-->>Dev: Present commit message

    Note over Dev,Redmine: Bug Evaluation Workflow (evaluate-bug.mdc)
    Dev->>Cursor: Request bug analysis (ticket ID)
    Cursor->>Redmine: Fetch ticket details
    Redmine-->>Cursor: Bug description, comments, similar issues
    Cursor->>Git: Search codebase (grep, git history)
    Git-->>Cursor: Affected files and changes
    Cursor->>Cursor: Root cause analysis
    Cursor->>Cursor: Generate visual diagrams
    Cursor-->>Dev: Complete bug analysis report