stacks-retro

Generating a development retrospective from git commit history requires analyzing standard conventional commit formatting to categorize work and calculate focus scores. The Skill automatically groups commits into work sessions based on a 45-minute inactivity threshold to highlight behavioral trends.

Git behavioral analytics measure engineering focus by analyzing commit history to calculate focus scores and identify patterns like test debt or maintenance-heavy workflows. This provides visibility into development patterns by transforming raw git history into structured, data-driven retrospectives.

Yes, standard conventional commit formatting is required to accurately categorize work and calculate development metrics. The Skill relies on this formatting structure to identify technical debt patterns and generate accurate behavioral retrospectives from your git history.

Yes, you can analyze a sprint's git history to balance feature development and technical debt. By running a retrospective report on recent development activity, the Skill identifies whether your engineering team maintains a healthy workflow balance between building new features and resolving maintenance-heavy work.

Session detection works by automatically grouping commits into discrete work sessions based on a 45-minute inactivity threshold. This grouping allows the behavioral analysis to accurately calculate focus scores and identify development patterns within specific periods of coding activity.

The best way to track contribution streaks using git analytics is to use a retrospective tool that transforms raw commit history into structured reports. It applies behavioral analysis to identify continuous development patterns and calculate workflow focus over time.