codecodebase analysis / analyze commits

Analyze Commits

analyze_commits

Analyzes local git commit history — authors, frequency, recent changes, and commit patterns. No API key required; reads directly from the local git repository. Use when: user asks about who committed what, recent changes, commit history, activity patterns, or wants to understand how a local repo has evolved. Scope: local git repository only — no network access. Run git commands via subprocess. Not for: remote GitHub repo metadata (use get_repo_info), fetching remote files (use get_file), or searching code patterns (use search_code).

How to use analyze_commits

Provide only the required inputs below. Start with the smallest scope that answers the task, then review the risk properties before an agent executes the call.

Risk and execution properties

Read only: yes

Destructive: no

Idempotent: yes

Open world: no — operates locally or through configured services

Inputs

pathstringrequired

Path to the local git repository root. Example: '/Users/me/my-project'

sincestring

Only show commits after this date. Accepts git date formats: '2024-01-01', '1 week ago', '3 months ago'. Optional.

untilstring

Only show commits before this date. Accepts git date formats. Optional.

authorstring

Filter commits by author name or email (partial match). Optional.

max_commitsinteger

Maximum number of commits to return. Default: 50.

Default: 50

Example input

{
  "path": "<string>",
  "since": "<string>",
  "until": "<string>",
  "author": "<string>",
  "max_commits": 50
}

Browse or search the full 74-tool reference to choose the smallest suitable capability.

Browse all tools →