Skip to content
Changelog
Edit
On this page

#Changelog

#0.4.2

The tool describes itself with one sentence everywhere, and its documentation moved onto selfdoc's .stricttools/ layout.

#Fixes

  • **The tool describes itself with one sentence everywhere, including --help.** The --help header, README, docs site and the npm and PyPI package metadata now carry the same description.

#0.4.1

Documentation frontmatter converted to TOML for the current selfdoc; no user-facing change.

#Infrastructure

  • Documentation frontmatter converted to TOML for the current selfdoc; no user-facing change.

#0.4.0

The documentation joins the unified site at https://smmh.dev/reposummary/, and the project describes itself consistently in its README, package documentation and registries.

#Features

  • Documentation joins the unified site at https://smmh.dev/reposummary/, and the project describes itself consistently. The same one-sentence definition now appears in the README, the site index, the Go package documentation and the PyPI and npm package metadata, and the wrapper manifests link the docs, issues and changelog.

#0.3.0

Effect classification and the framework flag quartet.

Context

reposummary moves onto go-strictcli 0.29.0, which makes effect classification mandatory: every command must declare whether it reads or writes. summarize declares itself mutating because it writes the rendered journal to --output. In exchange the framework now supplies --dry-run, --quiet and --verbose on every invocation, so those flags behave identically here and across the rest of the toolset instead of being per-command accidents.

#Features

  • Effect classification and the framework flag quartet. reposummary summarize now declares itself mutating, and --dry-run, --quiet and --verbose are provided by the framework on every invocation.

#0.2.0

Cache pruning, Windows support for npm/PyPI installs, and journal polish fixes.

#Features

  • Cache pruning. The on-disk journal cache now maintains itself: each write prunes entries not read in the last 90 days, and every cache hit refreshes an entry's timestamp so frequently-used journals stay warm.
  • Windows support. The npm and PyPI wrappers now install the prebuilt windows/amd64 and windows/arm64 binaries (downloading the .zip artifact and the .exe). Not yet CI-verified on a Windows runner.

#Fixes

  • Polish fixes. Date-range window headings now use the same → glyph as the subtitle; distinct empty windows no longer share a cache entry (which could serve a cached journal under the wrong heading); and --model values are passed to the backend verbatim (both short aliases like haiku and full model ids work).

#0.1.3

Documentation: a usage guide, selfdoc-managed README/CLAUDE, and clearer summarize --help.

#Features

  • Documentation. Added a usage guide (window forms, the three synthesis backends, and the caching model) and a cleaner generated README; reposummary summarize --help now has fully descriptive flag and argument text.

#0.1.2

Fix the CI/publish pipeline so npm and PyPI packages actually publish (ci-pypi working directory + goreleaser archive format).

#Infrastructure

  • Fix the CI/publish pipeline so npm and PyPI packages actually publish (ci-pypi working directory + goreleaser archive format).

#0.1.1

Fix the npm and PyPI publish pipeline so all three distribution channels work.

#Fixes

  • Working npm and PyPI packages. The 0.1.0 npm/PyPI publish was blocked by a CI failure; npm i -g reposummary and pip install reposummary now install the prebuilt binary correctly.

#0.1.0

Initial release of reposummary: a git activity journal generator.

Context

reposummary turns a repo's git history into a readable Markdown journal for any time window. The deterministic core needs no credentials; an optional LLM layer (claude CLI or Anthropic API) adds narrative prose. Distributed three ways from one repo: a Go binary (go install / GitHub releases), plus unscoped npm and PyPI packages that download the binary.

#Features

  • Initial release. Journal a git repository's activity over any time window (today, a date range like 2026-06-11+1month, an arbitrary git range, or full history) with grouped features/fixes, active-area churn, a timeline, and optional LLM narration via the claude CLI or Anthropic API. Ships as a Go binary, an npm package, and a PyPI package.

More tools from this site

  • claudestream Drive Claude Code from Python: run it as a subprocess and read its output as typed events, with async and sync sessions, sandbox policies, and tools you define in Python
  • claudewheel A TUI Claude Code Launcher that lets you have more than one profile, manage sessions lifecycle, pick the exact CC version, model to use (even older unlisted ones), pick which GitHub account to use, etc.
  • dirstat Fast, single-binary directory statistics CLI: every file under a tree grouped by format, with counts, sizes, and lines of code, as a colored terminal table or as JSON
  • fastware A batteries-included ASGI framework: msgspec JSON, a managed Granian server, dependency injection, SSE, WebSockets, auth, and a test client
  • go-toml-edit Zero-dep TOML editing library for Go with comment preservation
  • howmuchleft The fastest Claude Code statusline: context window, 5-hour, and weekly limit usage as three customizable gradient bars, rendering in about 6 ms
  • orxtra
  • pgdesign
  • predraw Declarative rendering pipeline: describe a scene in JSON and get SVG, PNG and WebP out, with light and dark style tokens, reusable components and text converted to path outlines
  • rlsbl 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
  • safegit git wrapper CLI that gives each commit its own temporary index and retries ref updates on conflict, so concurrent agents share one repository
  • saferm Command-line replacement for rm that archives every deletion with a mandatory reason and the context it ran in, so deleted files can be listed, inspected and restored
  • selfdoc Static Site Generator that builds a project's documentation site directly from its source code, so the docs can never drift from the code they describe, with SEO/AEO, first-class blog, search, and cross-project linking built in
  • strictcli
  • stricttest An always-on test-isolation floor: a pytest plugin and a Go env-hygiene module that make a test suite structurally unable to reach real credentials, the real HOME, the network, or the development repository.
  • wesktop A Python framework that turns an ASGI web app into a desktop application, serving it from a local Granian server and displaying it in a native OS window via pywebview
Search