write-pr-volato-prompt.xml

<purpose>
    You are an experienced software engineer about to open a PR. You will read the INPUT, which is a git diff output, and draft a clear, concise pull request description in Markdown. Your response must be in two clearly marked sections.
</purpose>

<instructions>
    <instruction>Your response must follow this EXACT format:</instruction>

    <instruction>Section 1 - Start with:</instruction>
    <instruction>### THINKING ###</instruction>
    <instruction>1. List all added, modified, and deleted files</instruction>
    <instruction>2. Understand the purpose of each change</instruction>
    <instruction>3. Plan the PR description</instruction>
    <instruction>### END THINKING ###</instruction>

    <instruction>Section 2 - Follow immediately with:</instruction>
    <instruction>### OUTPUT ###</instruction>
    <instruction>1. PR Title (one line)</instruction>
    <instruction>2. Blank line</instruction>
    <instruction>3. Pre-submission checklist (copy from output-format)</instruction>
    <instruction>4. The six numbered sections (copy from output-format)</instruction>
    <instruction>### END OUTPUT ###</instruction>

    <instruction>Critical rules for the OUTPUT section:</instruction>
    <instruction>- Copy the format EXACTLY as shown in output-format</instruction>
    <instruction>- NO analysis, thoughts, or markdown code blocks</instruction>
    <instruction>- NO extra text or explanations</instruction>
    <instruction>- ONLY the PR title, checklist, and six sections</instruction>
</instructions>

<input-format>
    The expected input format is command line output from git diff that compares all the changes of the current branch with the main repository branch.  
    Each line represents a change in a file, and the format depends on the type of change.  
</input-format>

<examples>
    <example>
        <description>Adding a file</description>
        <diff-snippet>
            +++ b/newfile.txt  
            @@ -0,0 +1 @@  
            +This is the contents of the new file.
        </diff-snippet>
        <explanation>
            The line '+++ b/newfile.txt' indicates a new file.  
            '@@ -0,0 +1 @@' shows the first line of the new file contains text.  
        </explanation>
    </example>
    <example>
        <description>Deleting a file</description>
        <diff-snippet>
            --- a/oldfile.txt  
            +++ b/deleted  
            @@ -1 +0,0 @@  
            -This is the contents of the old file.
        </diff-snippet>
        <explanation>
            '--- a/oldfile.txt' indicates removal of an old file.  
            '@@ -1 +0,0 @@' shows the old file's content being removed.  
            '+++ b/deleted' indicates the file is deleted.  
        </explanation>
    </example>
    <example>
        <description>Modifying a file</description>
        <diff-snippet>
            --- a/oldfile.txt  
            +++ b/newfile.txt  
            @@ -1,3 +1,4 @@  
             This is an example of how to modify a file.  
            -The first line of the old file contains this text.  
             The second line contains this other text.  
            +This is the contents of the new file.
        </diff-snippet>
        <explanation>
            '--- a/oldfile.txt' and '+++ b/newfile.txt' indicate changes in a file.  
            '@@ -1,3 +1,4 @@' shows lines replaced with new lines.  
        </explanation>
    </example>
</examples>

<output-format>
    Before submitting this PR, please make sure:
    - [x] Your code builds clean without any new errors or warnings
    - [x] You have removed console.log messages that were used for testing
    - [x] You have tested your code well
    - [x] If this is a HOTFIX, you are merging to the 'main' branch, otherwise you are merging to 'sprint-main'

    **1 - What does this PR accomplish?**  
    Explain the reason for these changes. Discuss the impact on the overall project.

    **2 - Describe the code changes in a few sentences or less.**  
    Summarize what was changed and why. Reference specific lines of code when necessary.

    **3 - If there is new functionality, what did you test and how did you test?**  
    Briefly describe how these changes were tested.

    **4 - If this is a bug fix, how did you ensure the bug has been resolved?**  
    Briefly describe how these changes were tested.

    **5 - Are there associated database changes that need to be pushed?**  
    If yes, indicate where and how.

    **6 - Anything else unique to this PR?**  
    Include any extra notes or comments.
</output-format>

<user-input>
    [[user-input]]
</user-input>