rlsbl
Go
Release orchestration and project scaffolding CLI that bumps versions, validates a structured JSONL changelog, tags only the commit CI verified, and publishes to npm, PyPI, Go and more.
reposummary
Turn a git repository's history into a Markdown journal: pick a time window or revision range and get a readable digest of what changed, optionally narrated by an LLM.
reposummary is a CLI that turns a git repository's history over a time window or revision range into a readable Markdown journal. It is for developers and AI agents who need an account of what a repository has been doing without reading the log commit by commit. Commit classification, churn per directory, issue references, authors, and tags all come straight from git, and an LLM is used only when you ask for an optional narrated layer. It is written in Go, with the source mirror at github.com/stricttools/reposummary.
Go cli 0.4.2
npm i -g reposummary
What it is
Turn a git repository's history into a Markdown journal: pick a time window or revision range and get a readable digest of what changed, optionally narrated by an LLM.
It is built for developers and AI agents who need a readable account of what a repository has been doing without walking the log commit by commit.
What it does
- Turns a git repository's history into a readable Markdown journal
- Pick a time window or a revision range
- Commit classification, per-directory churn, issue references, authors and tags are extracted deterministically from git
- An optional LLM prose layer, so tokens are spent only on narration
- Caching
Install
npm
npm i -g reposummary
PyPI
pip install reposummary
Package names
- Gostricttools.com/reposummary
- PyPIreposummary
- npmreposummary
More tools
safegit
Go
The Git CLI that is safe to hand to your AI Agents: no sharp edges by design, commit concurrency built-in, Git-compatible because it uses Git plumbing under the hood.
saferm
Go
The `rm` replacement that is safe to hand to your AI Agents: deleted files can be restored, know exactly which session deleted a file, when, and why, with the reason being a required flag.