Package Exports
- devbrief
- devbrief/dist/cli.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (devbrief) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
devbrief
Offline Git activity reports for your local machine. Scan one repo or every repo under folders you configure, see streaks and highlights, and optionally generate a LinkedIn post with Groq.
Install
npm install -g devbriefFor local development:
npm.cmd install
npm.cmd run build
npm.cmd run dev -- reportQuick Start
Run inside any Git repository:
devbrief report
devbrief report --week
devbrief report --monthConfigure machine-wide scanning:
devbrief init "D:\Work"
devbrief report --all --weekCheck setup:
devbrief doctorReports
devbrief report --format text
devbrief report --format markdown
devbrief report --format json
devbrief report --format markdown --save devbrief-reports\latest.md
devbrief report --all --format json --saveFilter report data:
devbrief report --mine
devbrief report --author "Your Name"
devbrief report --exclude-merges --exclude-bots
devbrief report --no-colorLinkedIn Posts
Save a Groq API key once:
devbrief config set-groq-key your_groq_api_key
devbrief config showGenerate or inspect a post:
devbrief post
devbrief post --style technical
devbrief post --dry-run-prompt
devbrief post --all --exclude-bots --save devbrief-reports\linkedin-post.txtUsing post sends a digest summary to Groq. Git history scanning stays local.
Config
devbrief config add-root "D:\Work"
devbrief config list-roots
devbrief config remove-root "D:\Work"
devbrief config clear-roots
devbrief config clear-groq-key
devbrief config pathConfig is stored in your user profile at .devbrief\config.json.
Development
npm.cmd run build
npm.cmd test
npm.cmd run dev -- report
npm.cmd pack:check