git
code_context_agent.tools.git ¶
Git history tools for codebase context analysis.
This module provides tools for extracting contextual information from git history: - Files changed together (coupling detection) - Commit history and messages - Diffs for understanding code evolution - Blame information for authorship context
These tools help understand: - Which files are coupled (change together frequently) - How code has evolved over time - Who has worked on what areas - The intent behind changes (via commit messages)
git_files_changed_together ¶
Find files that frequently change together with a given file (coupling detection).
USE THIS TOOL: - To identify tightly coupled files that may need to change together - To understand implicit dependencies not captured by imports - To find related files when making changes - To detect architectural coupling patterns
DO NOT USE: - For untracked files (not yet in git) - For files with no commit history
Analyzes git history to find files that appear in the same commits as the target file, ranked by co-occurrence frequency.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
file_path | str | Path to the file (relative to repo root or absolute). | required |
limit | int | Maximum number of commits to analyze (default 100). | 100 |
Returns:
| Type | Description |
|---|---|
str | JSON with: |
str |
|
str |
|
str |
|
Output Size: ~100 bytes per co-changed file.
Example success
{"status": "success", "file_path": "src/auth.py", "total_commits": 45, "cochanged_files": [{"path": "src/user.py", "count": 20, "percentage": 44.4}, ...]}
Example patterns detected
- High coupling (>50%): Files should possibly be merged or abstracted
- Medium coupling (20-50%): Normal feature-level coupling
- Low coupling (<20%): Incidental changes, less significant
Source code in src/code_context_agent/tools/git.py
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 | |
git_file_history ¶
Get commit history for a specific file.
USE THIS TOOL: - To understand how a file has evolved over time - To find when specific changes were introduced - To identify who has worked on a file - To trace the intent behind changes via commit messages
DO NOT USE: - For repository-wide history (use git_recent_commits instead) - For files not yet tracked by git
Returns recent commits that touched the specified file, including commit messages which often explain the "why" behind changes.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
file_path | str | Path to the file (relative to repo root or absolute). | required |
limit | int | Maximum commits to return (default 20). | 20 |
Returns:
| Type | Description |
|---|---|
str | JSON with commits array containing hash, author, date, and message. |
Output Size: ~200 bytes per commit.
Example success
{"status": "success", "file_path": "src/main.py", "commits": [{"hash": "abc123", "author": "dev@example.com", "date": "2024-01-15", "message": "Fix auth bug"}]}
Source code in src/code_context_agent/tools/git.py
150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 | |
git_recent_commits ¶
Get recent commits from the repository.
USE THIS TOOL: - To understand recent development activity - To identify active areas of the codebase - To see the general direction of development - To find commits relevant to a feature or bug
DO NOT USE: - For file-specific history (use git_file_history instead)
Returns recent commits from the specified branch with messages that provide context about development activity.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
limit | int | Maximum commits to return (default 30). | 30 |
branch | str | Branch or ref to query (default HEAD). | 'HEAD' |
Returns:
| Type | Description |
|---|---|
str | JSON with commits array containing hash, author, date, message, |
str | and files_changed count. |
Output Size: ~250 bytes per commit.
Example success
{"status": "success", "branch": "main", "commits": [{"hash": "abc123", "author": "dev@example.com", "date": "2024-01-15", "message": "Add feature X", "files_changed": 5}]}
Source code in src/code_context_agent/tools/git.py
234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 | |
git_diff_file ¶
Get the diff for a specific file.
USE THIS TOOL: - To see exact changes in a file - To understand what changed between commits - For code review or change analysis - To investigate recent modifications
DO NOT USE: - For large binary files - When you need full file content (use read_file_bounded instead)
Shows the unified diff for a file. Without a commit, shows unstaged changes. With a commit hash, shows changes introduced by that commit.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
file_path | str | Path to the file (relative to repo root or absolute). | required |
commit | str | None | Optional commit hash to show changes from that commit. | None |
context_lines | int | Lines of context around changes (default 3). | 3 |
Returns:
| Type | Description |
|---|---|
str | JSON with diff content and metadata. |
Output Size: Varies by change size, typically 1-10KB.
Example success
{"status": "success", "file_path": "src/main.py", "commit": "abc123", "diff": "@@ -10,5 +10,7 @@..."}
Source code in src/code_context_agent/tools/git.py
331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 | |
git_blame_summary ¶
Get authorship summary for a file.
USE THIS TOOL: - To identify who has expertise on a file - To understand code ownership distribution - To find the right person to ask about code - To see how recently different parts were modified
DO NOT USE: - For files not tracked by git - When you need line-by-line attribution (use git blame directly)
Provides a summary of who wrote which portions of a file, aggregated by author.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
file_path | str | Path to the file (relative to repo root or absolute). | required |
Returns:
| Type | Description |
|---|---|
str | JSON with author breakdown by lines owned. |
Output Size: ~100 bytes per author.
Example success
{"status": "success", "file_path": "src/main.py", "total_lines": 150, "authors": [{"email": "dev@example.com", "lines": 100, "percentage": 66.7, "last_commit_date": "2024-01-15"}]}
Source code in src/code_context_agent/tools/git.py
459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 | |
git_hotspots ¶
Identify frequently changed files (change hotspots).
USE THIS TOOL: - To find areas of high activity/churn - To identify potentially problematic code (frequent changes may indicate bugs) - To prioritize code review or refactoring efforts - To understand where development effort is concentrated
DO NOT USE: - For small repositories with little history
Analyzes git history to find files with the most commits, which often indicates areas of active development or instability.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
limit | int | Maximum commits to analyze (default 50). | 50 |
since | str | None | Optional date filter (e.g., "2024-01-01", "6 months ago"). | None |
Returns:
| Type | Description |
|---|---|
str | JSON with hotspots ranked by commit frequency. |
Output Size: ~80 bytes per file.
Example success
{"status": "success", "hotspots": [ {"path": "src/auth.py", "commits": 25, "percentage": 50.0}, {"path": "src/api.py", "commits": 15, "percentage": 30.0} ], "total_commits_analyzed": 50}
Interpretation
- High commit files may need: better tests, refactoring, or documentation
- Stable files (few commits) are often mature/well-designed
Source code in src/code_context_agent/tools/git.py
551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 | |
git_contributors ¶
Get contributor statistics for the repository.
USE THIS TOOL: - To identify key contributors and their areas of focus - To understand team structure and expertise distribution - To find domain experts for specific areas
DO NOT USE: - When you only need file-specific authorship (use git_blame_summary instead)
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
repo_path | str | Absolute path to the repository root. | required |
limit | int | Maximum commits to analyze (default 100). | 100 |
Returns:
| Type | Description |
|---|---|
str | JSON with contributors ranked by commit count. |
Output Size: ~100 bytes per contributor.
Example success
{"status": "success", "contributors": [ {"email": "dev1@example.com", "commits": 50, "percentage": 50.0, "first_commit": "2023-06-01", "last_commit": "2024-01-15"} ], "total_commits": 100}
Source code in src/code_context_agent/tools/git.py
644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 | |