git-status-report

Report Git repository and submodule synchronization status against remote tracking branches.

Updated Feb 22, 2026

Search Tags:#git #version control #repository #code management #submodule #sync status

Ready to run

npx skills add https://github.com/rahulrajaram/rahulskills --skill git-status-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-status-report
Source: https://github.com/rahulrajaram/rahulskills/tree/main/skills/git-status-report
Command: npx skills add https://github.com/rahulrajaram/rahulskills --skill git-status-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, consolidated view of the synchronization status between your local Git repositories (including submodules) and their remote origins, highlighting any discrepancies or pending changes.

Core Features & Use Cases

Comprehensive Status Reporting: Checks current branch, upstream tracking, ahead/behind counts, working tree status, and stash count for both the root repository and all submodules.
Drift Detection: Identifies when a submodule's HEAD commit differs from what the parent repository expects.
Use Case: Before deploying code or sharing changes, run this skill to ensure all parts of your project are in sync with their respective remotes, preventing unexpected integration issues.

Quick Start

Run the git-status-report skill to see the sync status of the current repository and its submodules.

Frequently Asked Questions about git-status-report

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

FAQPage Schema

How do I check if my git repository and submodules are in sync with remote tracking branches?▼

To check git repository sync status, you can run a report that analyzes your current branch, upstream tracking, ahead/behind commit counts, and working tree status for both the root repository and all submodules. It outputs a formatted ASCII table and summary highlighting any discrepancies or pending changes.

What is submodule pointer drift and how do I detect it in version control?▼

Submodule pointer drift occurs when a submodule's HEAD commit differs from what the parent repository expects. You can detect this drift by running a submodule sync status report, which identifies mismatches between the submodule's current checkout and the parent repository's recorded commit pointer.

How do I get a consolidated git status report before deploying code or sharing changes?▼

To get a consolidated git status report before deploying code, you can generate a comprehensive view that checks branch tracking, ahead/behind counts, working tree status, and stash count for both the root repository and all submodules, ensuring all parts of your project are in sync with their respective remotes.

Does the git status report include stash count and working tree status for submodules?▼

Yes, the git status report includes stash count and working tree status for submodules. It provides comprehensive status reporting that checks the current branch, upstream tracking, ahead/behind counts, working tree status, and stash count for both the root repository and all configured submodules.

What is the best way to visualize repository synchronization status across multiple git submodules?▼

The best way to visualize repository synchronization status across multiple git submodules is to generate a formatted ASCII table and summary. This report analyzes the current branch, upstream tracking, ahead/behind commit counts, and submodule pointer drift to provide a clear, consolidated view of all discrepancies.

Why does my submodule HEAD commit differ from what the parent repository expects?▼

Your submodule HEAD commit differs from what the parent repository expects due to submodule pointer drift. Running a sync status report identifies when a submodule's HEAD commit diverges from the parent repository's expected pointer, highlighting pending changes that need to be committed or updated.