branch-status

Summarize git branch merge status, divergence, and recent activity.

4|1|Updated Jan 8, 2024

Search Tags:#git #branch management #repository maintenance #divergence #merge status #release prep

Ready to run

npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill branch-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-status
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/branch-status
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill branch-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It quickly answers what is going on across your git branches (merged vs unmerged, how far ahead/behind they are from main, and when they were last updated) so you can decide what to keep, rebase, or clean up.

Core Features & Use Cases

Merged status & divergence from main: identifies which branches are fully merged and which still diverge from main.
Ahead/behind commit counts: reports how many commits each branch has advanced beyond main and how many it is missing.
Recency and tracking visibility: shows last activity and whether a remote tracking branch exists to support cleanup and coordination.
Use case: before a release, quickly review all active branches to locate stale work, confirm merges, and flag branches that need rebasing rather than guessing from scattered git history.

Quick Start

Run branch-status to get a table showing merged state, ahead/behind counts, last activity, and whether each branch has a remote counterpart.

Frequently Asked Questions about branch-status

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

FAQPage Schema

How do I check which git branches are ahead or behind main?▼

To check git branch divergence, you need a tool that queries ahead and behind commit counts relative to the main branch. This Skill summarizes branch health by reporting merged status, exact ahead/behind divergence, and last commit activity in a read-only dashboard.

What is the best way to find stale branches before a release?▼

Finding stale branches before a release requires reviewing recent commit activity and remote tracking status across local and remote branches. This Skill identifies unmerged branches and flags those lacking remote counterparts to support cleanup and coordination decisions.

Can I see if a local git branch has a remote tracking counterpart?▼

You can see remote tracking visibility by fetching and pruning remotes before executing git log and branch queries. This Skill displays whether each branch has a remote counterpart alongside its merged state and last activity timestamp.

How do I identify unmerged branches in my git repository?▼

Identifying unmerged branches involves comparing repository branch health against the main branch to determine merge status. This Skill produces a tabular dashboard showing which branches are fully merged and which still diverge from main.

Do I need to fetch and prune remotes to get accurate branch divergence?▼

Fetching and pruning remotes is required to get accurate branch divergence and tracking visibility. This Skill depends on executing git log, branch, and status queries after remote synchronization to generate a reliable read-only branch health table.