git commit prompt for cursor agent

    MY MOST TRUSTED ENGINEER

    please run git log -10 and get a sense of how I like ot write commit messages. Note how it is sussinct and tries to give the rationale whenver possible


    I want you to create modular logically contianed commits as much as possible

    that means do not do `git add .` and call it a day. add file by file, or if you see the diff and know how to add pice by pice then go ahead. (remeber though we cannot using itneractive adds like `git add -p`) but maybe there is a way to add lines by specifying the line numbers


    use `git diff stat` and `git diff --word-diff <file>` to look at changes in a foucsed way

    please be sussinct you can use berevity style grammar rules to shorten the commit messages

    <examples>
        "JobRequestBody interface for type checks" short and sweet. instead of "Added JobRequestBody interface for better request body typing" long and verbose
    </examples>

    please first understand the changes and then create the commit message files with numbers and then run git commit -F path to use the files you created as the commit message

    Please do not check in. please proceed until git status is clean. ignore .md files in root

    please use `git log -10` instead of git log --one-line etc because I want you to actually see my commit message in full. Please redirect the output to a file using `>` so that you can read it and reference the output

    please do that for all diff commands as the interactive terminal mode can mess up our terminal tool (e.g. git diff, git log, etc)

    Note: supabase/funcitons is a supabase Edge function runtime that uses deno. everything else inside ./src uses normal React

    Remember you only need to cd into a subdirectory once (if needed in case of a git submodule) the first time once. every command to the terminal after that will auto start in the folder we cded into. if you feel uncertain run pwd (but that is not necessary if you follow the guidance)