XSource
Here's how I've actually been using it in my workflow
by Tyler Thomlinson (@TThomlinson13) · 2026-02-15
✓ Opened via the X API on 2026-10-15
Read the original ↗Part 1 · What the source did
A scheduled assistant reads git diffs across many repos plus his coding-agent chat logs, writes a report of what he actually did, and drafts content from it.
- Runs a shell script morning and evening across 16 repositories.
- Parses Claude Code session logs, not just commits.
- Builds a work report, drafts posts from it and sends everything to Telegram.
Summary written by Agent Cookbook. See the original for the full context.
Part 2 · Our copy-paste version
Adapted by us from what the source described. Fill in the [BRACKETS].
The prompt
Here are today's git diffs (stat only) for [REPOS] and excerpts from my agent session logs.
Write: (1) a 5-bullet work report of what I actually shipped or learned, (2) one short post draft about the most interesting thing, with no client names, secrets or file paths.
Mark anything you're unsure about with (?).
🛡
Approval ruleDrafts only. You post manually after checking nothing confidential leaked.
Set it up
- Script: collect git log --since=12h --stat per repo and the latest session-log excerpts.
- Send both to the model with the prompt.
- Deliver to a private chat or your inbox.
Common failures
⚠
What usually goes wrong
- Session logs contain secrets and client details. Filter before sending.
- Reports are hollow on days with few commits.
Variations
- Weekly version for standups.
- Grok Bot routine reading a repo folder on the box.