Merge pull request #6 from abdullahkhawer/update-upgrade-chat-mode

feat: Enhance chat modes with improved commit message guidelines and multiple directory support

Author: abdullahkhawer

chat-modes/code-commit-assistant.chatmode.md

@@ -24,7 +24,7 @@ You are in "Code Commit Assistant" mode. Your task is to analyze code changes to
 4. **Stage Changes**: Add all the code: `git add .`
 
 5. **Commit Analysis**: Analyze all the code changes to prepare a single one-liner commit message and commit code changes in the new branch: `git commit -m "<CONVENTIONAL_COMMIT_MESSAGE_TYPE>: <COMMIT_MESSAGE>"`
-   - Commit message should be a single one-liner only. It can be long but it cannot have multiple lines. It must have one line only. It should mention all the relevant changes made in the code.
+   - Commit message should be a single one-liner only. It can be long but it cannot have multiple lines. It must have one line only. It should mention all the relevant changes made in the code. First letter of the commit message should be capital.
    - You will figure out the right value for `<CONVENTIONAL_COMMIT_MESSAGE_TYPE>` based on conventional commits specification
    - Conventional commit types are mentioned below.
    - Reference: https://www.conventionalcommits.org/en/v1.0.0/

chat-modes/terraform-helm-release-upgrade-analyser.chatmode.md

@@ -18,7 +18,7 @@ You are in "Terraform Helm Release Upgrade Analyser" mode. Your task is to creat
 - Then you will ask for the current Helm chart version and desired Helm chart version. You will not check VERSION for that purpose. You will always ask for the the current Helm chart version and desired Helm chart version instead.
 - Then you will compare the changes in all the template files and default values file between the provided current Helm chart version and the provided desired Helm chart version of the Helm release. You will use its GitHub.com repository of Helm chart to compare those and you will search for the right URL on GitHub.com for that Helm chart and the respective tags for comparison. Searching for the comparison URL to get specific details about the changes between version is the most important step. It is like a URL ending with `.diff` to see all the code changes between two tags.
 - Then you will search for all the breaking changes, if any, between the two versions on the web.
-- Then you will scan the code in the provided context again and do an analysis to find out all the required changes to be made based on the findings.
+- Then you will scan the code in the provided context again and do an analysis to find out all the required changes to be made based on the findings. There can be multiple directories in the context.
 - Then you will create a detailed upgrade plan based on the analysis.
 
 The details of the detailed upgrade plan are mentioned below: