git-recap

git-recap

Standups without the scramble

Your commits, ready for standup

git-recap reads local Git history and turns yesterday's work into a grouped, paste-ready summary — offline, private, and zero-dependency.

$ brew tap StackwiseTechnologiesLtd/tools && brew trust StackwiseTechnologiesLtd/tools && brew install git-recap
Install with HomebrewView on GitHub
git-recap
$ ▌
one command · smart categories · copy into standup notes

Features

From raw log to standup answer

Group commits, scan multiple repos, and ship a clean summary before the call starts.

Smart grouping

Grouped when you need it

Conventional commits and keyword heuristics sort your work into Features, Fixes, Docs, Refactors, and more — so standup answers are already categorized.

git-recap
$ ▌
grouped when you need it

Multi-repo

Scanned across projects

Run from a parent folder or pass multiple paths. git-recap aggregates only the repositories where you actually shipped commits in the timeframe.

git-recap
$ ▌
scanned across projects

Paste-ready

Clean output for Slack and notes

Use --plain for no colors and no hashes, or --summary-only when you want just the standup block. Copy once, paste into the call.

git-recap
$ ▌
paste-ready for Slack

Smart summaries

Features, fixes, chores — already sorted

Conventional commits and keyword heuristics classify your work so you talk about outcomes, not hash soup.

  • Category grouping

    Features, Fixes, Docs, Refactors, Tests, Performance, Chores, Other.

  • Readable bullets

    Prefixes stripped, long subjects shortened at word boundaries.

  • Time presets

    --today, --yesterday, --week, or any git --since expression.

    See usage →
git-recap
$ ▌
Routing
Inside a repo
Recaps the current project only.
Parent folder
Scans immediate subdirectories for .git.
Explicit paths
Pass the repos you care about by name or path.

Local & private

Entirely offline. Nothing leaves your machine.

Pure Bash + git plumbing. No Node runtime, no API keys, no telemetry — just your local author history for the window you choose.

  • Author-aware

    Matches git config user.email, then falls back to user.name.

  • --plain for Slack

    No colors, no hashes — paste straight into standup notes.

  • Zero dependencies

    A single executable script you can brew install or symlink.

Install

One brew away

Commands first — then the install line types itself out. Copy the brew command when you're ready.

git-recap — help

"Your commits, ready for standup"

$ git-recapsummarize current repo / scan cwd
$ git-recap [path]summarize a specific repo
$ git-recap --todaycommits since midnight
$ git-recap --yesterdayyesterday only
$ git-recap --weeklast seven days
$ git-recap --plainpaste into Slack / notes
$ git-recap --summary-onlystandup block only
$ git-recap -hshow help

install:

by Stackwise Technologies

$ brew tap StackwiseTechnologiesLtd/tools && brew trust StackwiseTechnologiesLtd/tools && brew install git-recap

Prefer source ? See docs.

Help

Everyday commands

The install panel above doubles as a quick reference. Full docs — timeframes, routing, and options — live on the docs page.

Frequently asked questions

What is git-recap?
git-recap is a zero-dependency Bash CLI that reads local Git history and turns your commits into grouped, paste-ready standup summaries — fully offline.
How do I install git-recap?
Install with Homebrew: brew tap StackwiseTechnologiesLtd/tools && brew trust StackwiseTechnologiesLtd/tools && brew install git-recap.
Does git-recap send data to a server?
No. By default git-recap only reads local .git state. Optional --reviews uses the authenticated GitHub CLI (gh) when you explicitly ask for PR reviews.
Can git-recap scan multiple repositories?
Yes. Run it from a parent folder to scan immediate subdirectories, pass paths as arguments, or use --recursive for deep scans.