commit-insights

Analyze commit activity, PR cycle times, and code churn for engineering health.

12|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/shogo-labs/shogo-ai --skill commit-insights
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-insights
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/engineering-pulse/.shogo/skills/commit-insights
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill commit-insights

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes engineering activity data to reveal team health and productivity insights from commit activity, PRs, and churn.

Core Features & Use Cases

  • Weekly engineering health metrics: track commits, PR cycle times, code churn, and contributor activity.
  • Team alignment and planning: provide a dashboard-ready summary for managers to guide sprint planning and capacity.
  • Use Case: When planning a release, you can compare last week's velocity to previous weeks to adjust scope.

Quick Start

Use the commit-insights skill to generate a weekly engineering health report from configured repositories.

Frequently Asked Questions about commit-insights

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track engineering health from commit activity and PR cycle times?

Track engineering health by analyzing commit activity, PR cycle times, and code churn to compute KPIs. This process monitors weekly velocity, contributor activity, and bottlenecks across multi-repo software teams to generate dashboard-ready summaries.

What is code churn and how does it impact team velocity analysis?

Code churn is the volume of code added, modified, or deleted in commits, serving as a key metric for team velocity analysis. Analyzing churn alongside PR cycle times identifies potential bottlenecks and highlights contributor activity patterns across repositories.

How do I generate a weekly engineering health report for sprint planning?

Generate a weekly engineering health report by computing KPIs from configured GitHub data sources, building dashboards, and persisting snapshots. Managers use these dashboard-ready summaries to compare weekly velocity against previous weeks and adjust release scope during sprint planning.

Can I monitor bottlenecks across multi-repo software teams using commit metrics?

Yes, you can monitor bottlenecks across multi-repo software teams by applying commit metrics to analyze PR cycle times and code churn. The system connects GitHub data sources, reads configuration from memory, and computes KPIs to reveal project-specific bottlenecks.

Does this engineering insights tool require connecting GitHub data sources to function?

Connecting GitHub data sources is supported to supply the commit activity, PR cycle times, and code churn data required for analysis. The system reads configuration from memory to compute KPIs and generate weekly engineering health reports for multi-repo teams.

Why should I analyze commit metrics instead of just tracking sprint story points?

Analyzing commit metrics provides objective, data-driven insights into actual engineering health by measuring code churn and PR cycle times. This reveals true team velocity and workflow bottlenecks across multi-repo projects, offering a more accurate reflection of capacity than subjective story point estimates.