Offline developer activity reports from your local Git repositories.
DevBrief scans one repo or every repo under folders you configure, summarizes your recent work, tracks streaks, exports clean reports, and can generate a LinkedIn-ready update with Groq. No GitHub token, GitHub account, or remote API is needed for Git scanning.
- Works fully offline for Git analysis.
- Scans a single repository or machine-wide project folders.
- Highlights commits, active days, streaks, authors, and top repos.
- Exports reports as text, Markdown, or JSON.
- Optionally turns your digest into a LinkedIn post with your Groq API key.
- Keeps config local in your user profile.
npm install -g devbriefCheck the install:
devbrief --version
devbrief doctorRun inside any Git repository:
devbrief report --weekExample output:
DevBrief
========
Offline Git activity digest
Scope: current repository
Range: since 7 days ago
Repo: C:/Users/You/Projects/devbrief
Summary
12 commits across 3 active days
Current streak 2 days
Longest streak 4 days
Most active day Wednesday
Top authors
Your Name 12
Recent highlights
- Add report export formats
- Improve machine-wide repository scanning
- Generate LinkedIn posts from digest context
Add a folder that contains your projects:
devbrief init "C:\Users\You\Projects"Then scan every Git repo under that folder:
devbrief report --all --weekManage scan roots:
devbrief config add-root "C:\Users\You\Projects"
devbrief config list-roots
devbrief config remove-root "C:\Users\You\Projects"
devbrief config clear-rootsDate ranges:
devbrief report --week
devbrief report --month
devbrief report --since "14 days ago"Filters:
devbrief report --mine
devbrief report --author "Your Name"
devbrief report --exclude-merges
devbrief report --exclude-botsOutput formats:
devbrief report --format text
devbrief report --format markdown
devbrief report --format jsonSave a report:
devbrief report --format markdown --save devbrief-reports\weekly.md
devbrief report --all --format json --saveDisable terminal color:
devbrief report --no-colorGit analysis is local. LinkedIn post generation is optional and sends a digest summary to Groq.
Save your Groq API key:
devbrief config set-groq-key your_groq_api_keyGenerate a post:
devbrief post --weekChoose a tone:
devbrief post --style humble
devbrief post --style punchy
devbrief post --style technicalInspect the prompt before sending anything to Groq:
devbrief post --dry-run-promptSave the generated post:
devbrief post --all --exclude-bots --save devbrief-reports\linkedin-post.txtDevBrief stores user config in your profile:
devbrief config pathThe config file is stored under:
C:\Users\<you>\.devbrief\config.json
Your Groq key is masked in config show:
devbrief config showNotes:
- Git scanning uses your local repositories.
- No GitHub token is required.
- Groq is only used when you run
devbrief post. devbrief post --dry-run-promptlets you inspect the exact prompt first.
devbrief report [options]
devbrief post [options]
devbrief init [root]
devbrief doctor
devbrief config <command>Useful help screens:
devbrief --help
devbrief report --help
devbrief post --help
devbrief config --helpgit clone https://github.com/ali-ab-2003/devbrief.git
cd devbrief
npm.cmd install
npm.cmd run build
npm.cmd test
npm.cmd run dev -- reportCheck the npm package contents:
npm.cmd run pack:checkMIT