JamesWare · Dev tool
DevPulse
A GitHub team recap you run in the terminal. HTML is only there if you need to share it.
Problem
GitHub already has the events. They are scattered across repos, PR lists, and contribution graphs. You want a weekly pulse without asking everyone to install a tool.
What it does
Syncs selected orgs and repos into SQLite with your token, then prints the recap in the terminal — team, person, repo, stale PRs, a playful weekly winner. Activity, not a score. The HTML page is a shareable dump of the same report, not the product.
Why it exists
One operator. One laptop. A CLI recap you actually want to look at.
Look
1 / 5 · Menu
Capabilities
- Setup walkthrough: PAT, orgs/repos, timezone, week mode
devpulsewith no args is a menu after first run- Today / week / month, person, repo, stale PRs
- Ink in the terminal; JSON and Markdown when you need them
- Optional HTML recap for sharing —
~/.devpulse/reports/ordevpulse web - Token at
~/.devpulse/token, mode 600 — never in git or SQLite
How it works
Your classic PAT (repo + read:org). Events land in local
SQLite. The recap is the CLI. Reports render from that store — they do not live-query
GitHub. If you need to send it to someone, it can also write a self-contained HTML page.
No hosted service. The team never installs anything.
Current state
In use locally. Not a git repo yet, not on GitHub, not an npm package. Awards name the metric (most commits), not “best engineer.”
Get it
Private checkout for now. After build: devpulse.