sup

Author: swaroopAkkineniWorkos

.cursor/commands/commit.md

@@ -0,0 +1,23 @@
+# Commit PR
+
+## Overview
+Add all files to the the commit. come up with a succinct, accurate commit message based on the commit. Then push that commit up as a branch. 
+
+## Steps
+1. **Add all changes to the commit **
+   - Add all changes to the commit 
+   - Ensure all changes are committed
+
+2. **Add a succinct commit message based on the changes made**
+   - Summarize changes clearly
+   - commit that message
+   - be succinct
+
+<!-- 3. TODO ADD PRETTY aND FORMAT STEP -->
+
+4.  **Push up branch**
+   - push commit to latest branch in origin
+
+## RULES YOU MUST FOLLOW
+   - never do this if you are in main. If so, alert the user that they are in main.  
+   - ignore all new generated .md files and do not add them to the branch. 

.cursor/commands/format.md

@@ -0,0 +1,34 @@
+# Format & Lint Changes
+
+## Overview
+
+Run all relevant formatting, linting, and prettifying commands before committing any changes.  
+This command ensures the codebase is clean and consistent by:
+
+- Formatting modified files
+- Linting modified files
+- Failing fast on any errors
+- Running tasks as efficiently and in parallel as safely possible
+
+> **Note:** This command is intended to be run *before* the `command.md` "Commit PR" flow.
+
+---
+
+## Steps
+
+### 1. Safety & Branch Checks
+
+1. Detect the current branch.
+2. **If on `main` (or the repository’s primary protected branch):**
+   - **Do not make any changes.**
+   - Surface a clear error:  
+     > "You are on `main`. Switch to a feature branch before running the format command."
+
+---
+
+### 2. Repository-Level Tidy (Default Workflow)
+
+From the **repository root**, run the standard repo-wide tidy command:
+
+```bash
+rush tidy --sha main

.cursor/commands/new-branch.md

@@ -0,0 +1,27 @@
+
+# Create a new branch
+
+## Overview
+Given a description for a task, create a new branch
+
+## Steps
+1. **Ingest the message put in and clean up the message**
+   - You must take in the message and clean it to be succinct and clear. 
+
+2. **Summarize the message into a branch**
+   - The branch should be relatively short, less than 63 characters
+   - if i provide a ticket number number like "ENT-1234" in the beginning, reference that at the beginning of the new summarize message. (ex: ENT-1234-my-branch)
+   - each word should be followed by - until the last word
+   - Validate that the branch name doesn't already exist
+   - Validate that the ticket number format is valid (e.g., numeric)
+   - Handle cases where the message is too long after summarization by truncating appropriately
+
+3. **Create the branch**
+   - using the message in step 2, create the branch
+   - If branch creation fails (e.g., branch already exists), inform the user and do not proceed
+
+## RULES YOU MUST FOLLOW
+   - never do this if there is no message given by the user
+   - never do this if the user does not provide a ticket number
+   - Validate all inputs before attempting branch creation
+   - Handle errors gracefully and provide clear feedback to the user

.cursor/commands/review-pr.md

@@ -0,0 +1,27 @@
+# PR Code Review Checklist
+
+## Overview
+You will perform a comprehensive checklist for conducting thorough code reviews to ensure quality, security, and maintainability. It should be scoped to the pr and how it changes the codebase and functionality of the app. 
+
+Ensure all rules, in ./cursor/rules/, are followed. 
+
+## Review Categories
+
+### Functionality
+- [ ] Code does what it's supposed to do
+- [ ] Edge cases are handled
+- [ ] Error handling is appropriate
+- [ ] No obvious bugs or logic errors
+
+### Code Quality
+- [ ] Code is readable and well-structured
+- [ ] Functions are small and focused
+- [ ] Variable names are descriptive
+- [ ] No code duplication
+- [ ] Follows project conventions
+
+### Security
+- [ ] No obvious security vulnerabilities
+- [ ] Input validation is present
+- [ ] Sensitive data is handled properly
+- [ ] No hardcoded secrets

.cursor/rules/.gitignore

@@ -0,0 +1,4 @@
+*
+
+!.gitignore
+!create-data-migration.mdc

.cursor/rules/create-data-migration.mdc

@@ -0,0 +1,16 @@
+---
+description: This rule creates a data migration Typescript class. It does not need to understand the underlying database.
+globs: 
+alwaysApply: false
+---
+
+
+# Required inputs
+- Name, which must be specified by the user
+
+# Steps
+- Generate an id by running ` pnpm exec node -e "const { ulid } = require('ulid'); console.log(ulid())"` in the `common/temp` directory and capturing the output. Do not use other ULID utilities. Trim any whitespace or newlines and convert the ulid to lowercase. I will refer to this as ULID.
+- Process the input name by converting it into kebab case. I will refer to this as NAME.
+- Create a new file called "<ULID>-<NAME>".ts in the 'packages/api/src/data-migrations/migrations'. This file should follow the class definition pattern of other files in that directory. Make sure to include a constructor that calls 'super()' with the ULID as the only argument.
+- Import the new class in 'packages/api/src/data-migrations/data-migration.jobs.module.ts' and add it to the `DATA_MIGRATION_MODULES` constant in alphabetical order.
+