ai(rules[cursor]) Don't add ref to commits (messy, repetitive, redundant)

Author: tony

.cursor/rules/git-commits.mdc

@@ -13,8 +13,6 @@ why: Explanation of necessity or impact.
 what:
 - Specific technical changes made
 - Focused on a single topic
-
-refs: #issue-number, breaking changes, or relevant links
 ```
 
 ## Component Patterns
@@ -83,7 +81,6 @@ what:
 - Integrate with existing Pane component logic
 - Document usage in Pane README
 
-refs: #485
 See also: https://example.com/docs/pane-capture
 ```
 
@@ -92,4 +89,4 @@ See also: https://example.com/docs/pane-capture
 fixed stuff and improved some functions
 ```
 
-These guidelines ensure clear, consistent commit histories, facilitating easier code review and maintenance.
+These guidelines ensure clear, consistent commit histories, facilitating easier code review and maintenance.

CLAUDE.md

@@ -213,8 +213,6 @@ why: Explanation of necessity or impact.
 what:
 - Specific technical changes made
 - Focused on a single topic
-
-refs: #issue-number, breaking changes, or relevant links
 ```
 
 Common commit types:
@@ -235,8 +233,6 @@ what:
 - Add remote_url parameter to add_repo function
 - Update CLI argument parser to accept --remote-url option
 - Add tests for the new functionality
-
-refs: #123
 ```
 
 ## Debugging Tips