feat: add include_patch parameter to get_commit tool

[voki-gandzhelashvili-t]

Summary

This PR adds a new optional parameter include_patch to the get_commit tool, allowing users to optionally include the patch/diff content for each file in the response.

Key Design Decision: Opt-in Behavior

The patch content is not included by default (include_patch: false). This is intentional:

• Non-breaking change: Existing integrations continue to work unchanged
• Performance conscious: Patch content can be large and may not always be needed
• Explicit control: Users opt-in when they need the actual diff content

Changes

1. Added Patch string field to MinimalCommitFile struct
2. Added include_patch boolean parameter to get_commit tool (default: false)
3. Updated convertToMinimalCommit function to conditionally include patch content

Usage

// Get commit without patch (default behavior, unchanged)
get_commit(owner: "foo", repo: "bar", sha: "abc123")

// Get commit with patch content
get_commit(owner: "foo", repo: "bar", sha: "abc123", include_patch: true)

Example Response with include_patch: true

{
  "sha": "abc123...",
  "files": [{
    "filename": "src/example.go",
    "status": "modified",
    "additions": 5,
    "deletions": 2,
    "changes": 7,
    "patch": "@@ -10,6 +10,9 @@\n func example() {\n+    // new code\n+    return true\n }"
  }]
}

Use Cases

• Code review automation tools
• AI agents analyzing code changes
• Commit analysis and auditing tools
• Any consumer that needs to see what actually changed in a commit

Test Plan

• Code compiles successfully
• Existing tests pass
• Manual testing confirms:
  • Default behavior unchanged (no patch in response)
  • `include_patch: true` includes patch content