Commit Insights

Analyze git activity and produce engineering health metrics. Use the gh CLI — do not connect GitHub.

1. Auth — exec({ command: "gh auth status" }). If not authenticated, ask for a PAT, save GITHUB_TOKEN to .env, retry.
2. Configure — Read tracked repos and team from memory (key: git_insights_config)
   • Repos to analyze, team member GitHub usernames
   • If not configured, ask the user which repos/team to track
3. Fetch data — For each configured repo (-R owner/repo):
   • exec({ command: "gh api repos/OWNER/REPO/commits?since=..." })
   • exec({ command: "gh pr list -R OWNER/REPO --state all --limit 100" })
   • PR details: gh pr view NUMBER --json createdAt,mergedAt,reviews
4. Compute metrics —
   • Weekly commits: total and per-developer breakdown
   • PR cycle time: median time from PR open to merge
   • Time to first review: median time from PR open to first review comment
   • Code churn: files changed frequently (>3 times in a week)
   • PR aging: open PRs sorted by age, flagging those >3 days without review
   • Top contributors: ranked by commits + reviews
5. Build canvas — Create or update the insights dashboard:
   • KPIs: weekly commits, avg PR cycle time, top contributor, active PRs
   • Team leaderboard table (developer, commits, PRs merged, reviews given)
   • PR aging table (PR title, author, age, status, reviewers)
   • Code churn hotspots (files changed most frequently)
6. Weekly report — On weekly heartbeat:
   • Compile full engineering health report
   • Compare to previous week (trending up/down)
   • Post to configured channel via send_message
7. Persist — Save weekly snapshots to memory for trend analysis