feat: Add code-reviewer chat mode, update README.md accordingly and create slower demos in gif format.

Author: Abdullah Khawer

README.md

@@ -17,23 +17,40 @@ Custom chat modes allow you to modify GitHub Copilot's behavior in VS Code. Each
 
 | Title | Description | Category |
 | ----- | ----------- | -------- |
-| [Terraform Helm Release Upgrade Analyser](chat-modes/terraform-helm-release-upgrade-analyser.chatmode.md) | Creates a detailed upgrade plan for a Helm release created via Terraform by analysing the configuration differences between the current and desired Helm chart versions and any breaking changes | Infrastructure & DevOps |
+| [Code Reviewer](chat-modes/code-reviewer.chatmode.md) | Analyzes code changes between two branches to perform comprehensive code reviews and suggest improvements for security, performance, and code quality | Development Tools |
+| [Code Commit Assistant](chat-modes/code-commit-assistant.chatmode.md) | Analyzes code changes, prepares conventional commit messages, and commits to a new branch with proper Git workflow automation | Development Tools |
 | [Dockerfile Developer](chat-modes/dockerfile-developer.chatmode.md) | Develops optimized, secure, and best-practice Dockerfiles based on user requirements and application context | Infrastructure & DevOps |
+| [Terraform Helm Release Upgrade Analyser](chat-modes/terraform-helm-release-upgrade-analyser.chatmode.md) | Creates a detailed upgrade plan for a Helm release created via Terraform by analysing the configuration differences between the current and desired Helm chart versions and any breaking changes | Infrastructure & DevOps |
 | [Conversation to Chat Mode](chat-modes/conversation-to-chat-mode.chatmode.md) | Creates a custom chat mode file based on a conversational interface where users describe their specific task requirements and guidelines | Development Tools |
-| [Code Commit Assistant](chat-modes/code-commit-assistant.chatmode.md) | Analyzes code changes, prepares conventional commit messages, and commits to a new branch with proper Git workflow automation | Development Tools |
 
-## Terraform Helm Release Upgrade Analyser
+## Code Reviewer
 
-This chat mode helps you safely upgrade Helm releases managed by Terraform by:
+This chat mode helps you perform comprehensive code reviews by analyzing changes between Git branches and providing detailed feedback by:
 
-- **Automatic Detection**: Scans your Terraform code to identify Helm release resources
-- **Version Comparison**: Compares template files and default values between chart versions
-- **Breaking Change Analysis**: Identifies potential breaking changes and compatibility issues
-- **Detailed Planning**: Creates comprehensive upgrade plans with step-by-step instructions
+- **Branch Comparison**: Analyzes code differences between source and target branches using Git diff
+- **Security Analysis**: Checks for secrets exposure, SQL injection vulnerabilities, and security best practices
+- **Performance Review**: Identifies inefficient algorithms, memory leaks, and unnecessary computations
+- **Code Quality**: Looks for code smells, duplicate code, complex functions, and formatting issues
+- **Best Practices**: Verifies proper error handling, logging, and documentation standards
+- **Targeted Suggestions**: Provides specific code snippets with improvements, file paths, and line numbers
 
 ### Demo
 
-![Demo](demos/terraform-helm-release-upgrade-analyser.chatmode.gif)
+![Demo](demos/code-reviewer.chatmode.gif)
+
+## Code Commit Assistant
+
+This chat mode helps you automate your Git workflow by analyzing code changes and creating proper commits by:
+
+- **Automatic Code Analysis**: Analyzes all uncommitted changes to understand the scope and impact of modifications
+- **Conventional Commits**: Automatically determines the appropriate conventional commit type (feat, fix, docs, etc.) based on code changes
+- **Branch Management**: Creates new branches for your changes following Git best practices
+- **Quality Checks**: Optionally runs pre-commit hooks and Terraform formatting before committing
+- **Automated Workflow**: Handles the complete Git workflow from branch creation to pushing changes
+
+### Demo
+
+![Demo](demos/code-commit-assistant.chatmode.gif)
 
 ## Dockerfile Developer
 
@@ -49,6 +66,19 @@ This chat mode helps you create optimized, secure, and production-ready Dockerfi
 
 ![Demo](demos/dockerfile-developer.chatmode.gif)
 
+## Terraform Helm Release Upgrade Analyser
+
+This chat mode helps you safely upgrade Helm releases managed by Terraform by:
+
+- **Automatic Detection**: Scans your Terraform code to identify Helm release resources
+- **Version Comparison**: Compares template files and default values between chart versions
+- **Breaking Change Analysis**: Identifies potential breaking changes and compatibility issues
+- **Detailed Planning**: Creates comprehensive upgrade plans with step-by-step instructions
+
+### Demo
+
+![Demo](demos/terraform-helm-release-upgrade-analyser.chatmode.gif)
+
 ## Conversation to Chat Mode
 
 This meta chat mode helps you create new custom chat modes through a guided conversation by:
@@ -62,20 +92,6 @@ This meta chat mode helps you create new custom chat modes through a guided conv
 
 ![Demo](demos/conversation-to-chat-mode.chatmode.gif)
 
-## Code Commit Assistant
-
-This chat mode helps you automate your Git workflow by analyzing code changes and creating proper commits by:
-
-- **Automatic Code Analysis**: Analyzes all uncommitted changes to understand the scope and impact of modifications
-- **Conventional Commits**: Automatically determines the appropriate conventional commit type (feat, fix, docs, etc.) based on code changes
-- **Branch Management**: Creates new branches for your changes following Git best practices
-- **Quality Checks**: Optionally runs pre-commit hooks and Terraform formatting before committing
-- **Automated Workflow**: Handles the complete Git workflow from branch creation to pushing changes
-
-### Demo
-
-![Demo](demos/code-commit-assistant.chatmode.gif)
-
 # 📖 How to Use Chat Modes
 
 To use any of these custom chat modes effectively, follow these general steps:

chat-modes/code-reviewer.chatmode.md

@@ -0,0 +1,67 @@
+---
+description: Analyze code changes between two branches to do a code review and suggest changes if required
+tools: ['runCommands']
+model: Claude Sonnet 4
+---
+
+# Code Reviewer Mode
+
+You are in "Code Reviewer" mode. Your task is to analyze code changes between two branches to do a code review and suggest changes if required by running all the commands as per the instructions and guidelines on behalf of the user in the directory selected as the context.
+
+## Prerequisites
+
+- You need to add context which is a directory having code changes. If the context is missing then you will not proceed further and ask the user to add the right context until it is provided.
+
+## Instructions and Guidelines
+
+1. **Ask for Source Branch**: Ask for source branch name from the user if not provided upfront.
+
+2. **Ask for Target Branch**: Ask for target branch name from the user if not provided upfront.
+
+3. **Find Changed Files**: Use the following command to find all the changed files: `git diff --name-only <SOURCE_BRANCH> <TARGET_BRANCH>`
+
+4. **Code Review Analysis**: Analyze all the code changes in each changed file to do a comprehensive code review based on the following guidelines:
+   - Share only code snippets that need changes with specific suggestions along with file path and line numbers.
+   - Check for secrets exposure, SQL injection, vulnerabilities.
+   - Identify inefficient algorithms, memory leaks, unnecessary computations.
+   - Look for code smells, duplicate code, complex functions, trailing whitespaces.
+   - Verify proper error handling, logging, documentation.
+
+You can ask the questions specified above to the user as follows:
+```
+Kindly let me know:
+
+1. Source Branch: What is the name of the source branch (the branch with new changes)?
+2. Target Branch: What is the name of the target branch (usually main/master)?
+```
+
+## Example Usage
+
+To use this chat mode effectively, follow these steps:
+
+### Prerequisites
+
+- Ensure you have a Git repository with both the source and target branches
+- Know what source branch and target branch you want to use for your code review
+- Ensure the directory having code changes is added as the context
+
+### Prompt Examples
+
+**Option 1: Let the mode prompt you with all the questions**
+
+```
+Start.
+```
+
+**Option 2: Provide answers upfront**
+
+```
+Source Branch: feature/new-feature
+Target Branch: master
+```
+
+## Disclaimers
+
+- **Git Repository Required**: This chat mode requires an active Git repository with both the source and target branches
+- **Code Analysis**: The assistant will analyze your code changes to do a code review and suggest changes if required
+- **Potential Token Usage**: This chat mode may incur additional token usage, which could impact your usage limits or costs depending on your AI service plan