| schema_version | 1 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | commit-digest | ||||||||||||||||
| slug | commit-digest | ||||||||||||||||
| description | End-of-day rollup of every commit across local git repos. Runs entirely on the customer's machine — no cloud, no tokens, no secrets. | ||||||||||||||||
| access | private | ||||||||||||||||
| runtime | local | ||||||||||||||||
| vault | local | ||||||||||||||||
| schedule | 0 18 * * 1-5 | ||||||||||||||||
| secrets | |||||||||||||||||
| surfaces |
|
||||||||||||||||
| render | inline | ||||||||||||||||
| artifact_dir | ~/Documents/commit-digests | ||||||||||||||||
| events_schema |
|
A local end-of-day digest. At 18:00 on weekdays it walks every git repo under ~/code (configurable), collects today's commits, and writes a one-page summary you can read in 30 seconds.
Designed to run with runtime: local — no API keys, no vaults, no network calls. The whole thing executes as a subprocess on the customer's laptop.
- Discover repos: every directory under
~/codecontaining a.gitfolder. Configurable via theCOMMIT_DIGEST_ROOTenvironment variable. - For each repo with commits today:
- List commits as
<short-sha> <author> — <subject> - Write a one-paragraph synthesis: what shipped, what's in flight, what stalled
- List commits as
- Flag suspicious patterns:
- Commits whose subject contains
WIP,fixup!,squash!, ortmp - Branches with uncommitted changes older than 24 hours (forgotten work)
- Repos with unpushed commits older than 48 hours (stuck on local)
- Commits whose subject contains
- If more than 20 repos have activity, group by top-level folder under
~/codeand summarize per group instead of per repo. - Render the digest to the terminal. Also write a dated markdown file to
~/Documents/commit-digests/YYYY-MM-DD.md. - If
SMTP_HOSTis set in the environment, email a copy to the user's gituser.email.
- The local filesystem under
COMMIT_DIGEST_ROOT(default~/code). - Local
gitbinary (any version ≥ 2.0). - Optional:
SMTP_HOST,SMTP_USER,SMTP_PASSfrom the environment for email delivery. Stored by the OS, not by the app.
No secrets declared in secrets: because nothing crosses the network on the app's behalf — the SMTP variables (if used) are read directly from os.environ by the runtime.
- Terminal: full digest, color-coded by flag severity.
- File:
~/Documents/commit-digests/YYYY-MM-DD.md(also theartifact_dir). - Email (optional): plain-text copy of the markdown file.
- Event:
digest_emittedwith counts so a downstream observer can chart productivity over time. - Event:
forgotten_branch_detectedper stale branch — the runtime can route these to a follow-up app (e.g. a "remind me Monday" reminder).
access: private— never shared, never indexed.- Reads only — never runs
git commit,git push, or any state-mutating git operation. - Skips repos where the working tree contains files matching the user's global
.gitignorepatterns marked secret (e.g..env,*.pem). - If a repo's HEAD detached or in an interactive rebase, the digest notes the state and skips the commit walk for that repo.
- If
~/codedoes not exist, the app exits cleanly withdigest_emitted{repo_count: 0}rather than erroring.
This is the canonical case for runtime: local: an app that touches files the customer wouldn't want crossing a network boundary (their commit history, authored code, in-flight branches), needs no shared infrastructure, and benefits from running where the source of truth already lives.
Compare to subprocess (shared backend) or ec2 (sandboxed cloud) — both would require shipping the customer's git history off-machine to be useful, which most engineers will not do for a digest tool.