Commit Analyzer

**Judgement:** A focused, practical git-based health monitor for autonomous workflows that appears well thought-out and useful if you accept its opinionated metrics and thresholds. **What it does well** - Converts git commit history into clear health indicators (healthy / warning / critical) using commits/hour, learning percentage, idle gaps, and daily averages. - Offers several complementary commands: quick health check, full multi-day report, hourly breakdown, category analysis, and explicit waiting-mode detection. - Provides specific, documented thresholds and example outputs, plus JSON mode for tool integration and a suggested HEARTBEAT.md pattern. **Key risks / limitations** - Relies entirely on commit patterns; if your workflow doesn’t commit frequently or uses squash/monorepo practices, signals can be misleading. - Heavily opinionated thresholds (e.g., 3–6 commits/hour as “healthy”) may not generalize across projects, teams, or agent designs and may require manual tuning. - Reliability and robustness are unclear from the description (no tests, edge-case handling, or platform assumptions documented), so behavior on atypical git histories is unknown. **Recommended scenarios** - You run autonomous or semi-autonomous coding agents and want a lightweight, git-native heartbeat/health signal. - You maintain a personal or small-team repo with frequent granular commits and want to track learning vs execution balance over time. - You plan to wire git-based health checks into dashboards, alerting, or periodic HEARTBEAT.md routines using the JSON output mode. - You are comfortable treating this as a heuristic signal, not a ground-truth productivity or reliability metric, and are willing to adapt thresholds to your context.