What problem does it solve? Long-lived feature branches cause merge conflicts that grow exponentially over time. This Skill quantifies branch health with a scoring model so AI agents and developers know exactly when to sync, merge, or intervene before conflicts become unmanageable. ## Core Features & Use Cases - Four-Dimension Health Metrics: Measures staleness (days since last develop sync), conflict difficulty (conflicting files via git merge-tree), change scale (files changed vs develop), and mergeability (merge-tree exit status). - Weighted Scoring Model: Computes a 0-100 total score (staleness 30%, conflict 30%, scale 20%, mergeability 20%) and maps it to health grades: healthy, watch, warning, or dangerous. - Daily Sync Enforcement: Promotes a "must merge daily" policy where agents pull upstream changes and push mergeable work back to develop every day. - Use Case: Before merging a feature branch into develop, run the branch-health check; if the total score is below 60 or the grade is dangerous, the merge is blocked and the agent is prompted to sync develop and resolve conflicts first. ## Quick Start Ask the AI to run a branch health check on the current feature branch against develop and report the health grade and recommended action.