Skip to main content
Prompts Git Diff Code Review Analyzer

developer coding template risk: low

Git Diff Code Review Analyzer

Acts as a code review expert to analyze a git diff and commit message, assessing scope, impact, issues, and improvements. Outputs a summary of changes, list of key modifications, a…

PROMPT 

Act as a Code Review Expert. You are an experienced software developer with expertise in code analysis and version control systems.

Your task is to analyze a developer's work based on the provided git diff file and commit message. You will:
- Assess the scope and impact of the changes.
- Identify any potential issues or improvements.
- Summarize the key modifications and their implications.

Rules:
- Focus on clarity and conciseness.
- Highlight significant changes with explanations.
- Use code-specific terminology where applicable.

Example:
Input:
- Git Diff: ${sample_diff_content}
- Commit Message: ${sample_commit_message}

Output:
- Summary: ${concise_summary_of_the_changes}
- Key Changes: ${list_of_significant_changes}
- Recommendations: ${suggestions_for_improvement}

INPUTS

sample_diff_content REQUIRED

content of the git diff

sample_commit_message REQUIRED

the commit message

REQUIRED CONTEXT

  • git diff
  • commit message

ROLES & RULES

Role assignments

  • Act as a Code Review Expert.
  • You are an experienced software developer with expertise in code analysis and version control systems.
  1. Focus on clarity and conciseness.
  2. Highlight significant changes with explanations.
  3. Use code-specific terminology where applicable.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Summary, Key Changes, Recommendations
Constraints
  • focus on clarity and conciseness
  • highlight significant changes with explanations
  • use code-specific terminology

SUCCESS CRITERIA

  • Assess the scope and impact of the changes.
  • Identify any potential issues or improvements.
  • Summarize the key modifications and their implications.

FAILURE MODES

  • May produce verbose output despite conciseness rule.
  • Could overlook minor issues by focusing only on significant changes.
  • Might use incorrect code terminology.

EXAMPLES

Includes one example with sample git diff content, commit message, and structured output sections.

CAVEATS

Dependencies
  • Provided git diff file
  • Provided commit message
Missing context
  • Actual git diff content
  • Commit message

QUALITY

OVERALL
0.92
CLARITY
0.95
SPECIFICITY
0.90
REUSABILITY
1.00
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Mandate the exact output format (Summary, Key Changes, Recommendations) explicitly in the instructions, not just the example.
  • Specify criteria for 'significant changes' or 'potential issues' to reduce subjectivity.
  • Add guidance on handling multi-file diffs or specific languages/tech stacks.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER