dcdpr / jp / 25800698068

65%

push

github

chore(tools): Add `git_blame` tool to project tooling (#631)

Implements a `git_blame` tool backed by `git blame --porcelain`,
exposing per-line authorship over a bounded line range to the assistant
during pair-programming sessions.

Output is grouped by commit: consecutive lines that share the same
blamed commit are collapsed into a single hunk, so token cost scales
with the number of distinct commits rather than the number of lines.
Each hunk carries `hash`, `short_hash`, `author`, `date`, `summary`, and
— when present — a `previous` field containing the commit that owned
those lines before the current change. That lets the assistant drill
back through line history with a follow-up `git_show` or
`git_diff_commit` call without an extra blame invocation.

The range is capped at 200 lines per call. Validation rejects zero-based
start lines, inverted ranges, and oversized windows with a clear error
message before any subprocess is spawned. An optional `revision`
parameter allows blaming at any commit, tag, or branch;
`ignore_whitespace` passes `-w` through to git.

The tool is wired into the MCP tool registry and added to the
git-reading skill so it is available whenever that skill is active.

---------

Signed-off-by: Jean Mertz <git@jeanmertz.com>

211 of 246 new or added lines in 5 files covered. (85.77%)

26027 of 39144 relevant lines covered (66.49%)

218.05 hits per line