Cursor rule

1---
2description: Rules for various git actions that happen with this project. 
3globs: 
4---
5 
6# Creating Branches
7 
8Branch names should go by the following structure (anything in "{}" brackets is a placeholder). "{short-slug}" should be replaced with a short name that best describes the changes - do ask for confirmation if needed.
9- `release/{version}` for release branches.
10- `refactor/{short-slug}` for refactors.
11- `test/{short-slug}` for changes that are only test updates or additions.
12- `fix/{short-slug}` for changes that fix a bug. Prompt the user for the issue number the fix is for and include that in the branch name.
13- `add/{short-slug}` for changes that are adding a new feature.
14 
15# Commits
16 
17Make sure each commit addresses an atomic unit of work that independently works.
18 
19Make sure the commit message has a subject line which includes a brief description of the change and (if needed), why it was necessary. Write the subject in the imperative, start with a verb, and do not end with a period. The subject line should be no longer than 50 characters.
20 
21There must be an empty line between the subject line and the rest of the commit message (if any). The commit body should be no longer than 72 characters.
22 
23The commit message should explain what caused the problem and what its consequences are (if helpful for understanding the changes).
24 
25The commit message should explain how the changes achieve the goal, but only if it isn't obvious.
26