Git (Submodule) Assistant
ExtensionFreeVS Code extension that detects common git (and submodule) issues and helps to solve them
Capabilities9 decomposed
protected-branch-violation-detection
Medium confidenceMonitors the currently checked-out git branch against a configurable list of protected branch names (e.g., 'master', 'main', 'production') and emits VS Code notifications when the user switches to or is working on a protected branch. Uses git state polling integrated with VS Code's git extension to read the current HEAD branch and compares it against user-defined protection rules stored in extension settings. Allows users to switch branches directly from the notification UI without leaving the editor.
Implements branch protection as a lightweight, configurable local warning system integrated directly into VS Code's notification UI, allowing users to define custom protected branch lists without relying on remote repository settings or git hooks.
Simpler and faster than enforcing branch protection via GitHub/GitLab settings because it provides instant local feedback without network calls, though it lacks server-side enforcement guarantees.
unpushed-commit-prevention-on-editor-close
Medium confidenceIntercepts VS Code closure via keyboard shortcut (`Ctrl+Q` on Windows/Linux, `Cmd+Q` on macOS) and checks for unpushed commits in the current branch by querying git state through VS Code's git extension. If unpushed commits are detected, displays a modal dialog offering options to push commits before closing or force-close without pushing. Uses VS Code's `onBeforeShutdown` lifecycle hook to block closure until the user makes an explicit choice.
Leverages VS Code's `onBeforeShutdown` lifecycle hook to inject a synchronous blocking check for unpushed commits at editor closure time, providing a last-chance safety net without requiring explicit user commands or git hooks.
More user-friendly than git pre-commit hooks because it provides a clear dialog with options rather than silently blocking closure, and it integrates directly into the editor's shutdown flow rather than requiring separate git configuration.
post-commit-push-notification
Medium confidenceDetects when a commit is created in the current branch (via git state polling or VS Code git extension events) and immediately displays a notification prompting the user to push the commit to the remote repository. Includes an optional auto-push feature that can be configured to automatically push commits without user interaction, or can be set to notification-only mode where the user must manually trigger the push.
Provides a configurable post-commit workflow automation that can operate in either notification-only or auto-push mode, integrating directly with VS Code's git extension to detect commits without requiring git hooks or external tools.
Simpler than git hooks because it's configured entirely within VS Code settings and doesn't require shell script knowledge, and it provides immediate visual feedback via notifications rather than silent background execution.
remote-sync-polling-with-auto-fetch
Medium confidenceRuns a background polling loop (at configurable intervals, triggered on VS Code startup and periodically thereafter) that executes `git fetch` to check if the remote repository has new commits that the local branch is behind on. When out-of-sync status is detected, displays a notification to the user. Includes an optional auto-fetch feature that automatically runs `git fetch` when the workspace has no local uncommitted changes, reducing the need for manual fetch commands.
Implements event-driven remote synchronization via polling with a conservative auto-fetch strategy that only runs when the workspace is clean, reducing the risk of fetch-induced merge conflicts while maintaining background awareness of remote changes.
More lightweight than file-watching approaches because it uses git's native fetch mechanism rather than monitoring filesystem changes, and the configurable polling interval allows teams to balance responsiveness against resource usage.
submodule-auto-initialization
Medium confidenceDetects when a git repository contains submodule definitions (via `.gitmodules` file or git config) and automatically runs `git submodule init` and `git submodule update` commands to initialize and populate submodule directories. Runs on workspace open or when submodule configuration changes are detected, ensuring submodules are ready for use without requiring manual terminal commands.
Provides automatic submodule initialization on workspace open without requiring explicit user commands, integrating with VS Code's workspace lifecycle to ensure submodules are ready before the user begins editing.
More convenient than manual `git submodule init && git submodule update` commands because it runs automatically on workspace open, and it's more discoverable than git hooks because it's configured entirely within the VS Code extension.
submodule-auto-update
Medium confidenceMonitors submodule state and automatically runs `git submodule update` to pull the latest commits from submodule remote repositories at configurable intervals or when submodule configuration changes are detected. Can be configured to run only when the workspace has no local changes (conservative mode) or more aggressively on a fixed schedule.
Provides configurable automatic submodule updates with optional conservative mode that only updates when the workspace is clean, reducing the risk of update-induced conflicts while maintaining synchronization.
More proactive than manual submodule updates because it runs on a schedule or trigger, and it's more integrated than git hooks because it's configured entirely within VS Code and provides visual feedback via notifications.
git-state-polling-and-event-integration
Medium confidenceImplements a background polling mechanism that periodically queries git repository state (current branch, unpushed commits, remote sync status, submodule state) by invoking git commands through VS Code's git extension API. Integrates with VS Code lifecycle events (workspace open, shutdown, focus change) to trigger state checks at appropriate times and coordinate with other extension capabilities. Polling interval is configurable to balance responsiveness against resource usage.
Implements a unified polling infrastructure that coordinates multiple extension features (branch protection, unpushed commits, remote sync, submodule management) through a single background service, reducing resource overhead compared to independent polling per feature.
More resource-efficient than independent polling per feature because it centralizes state queries, and it's more responsive than manual git status checking because it runs continuously in the background.
configurable-feature-toggles-and-parameters
Medium confidenceProvides a settings UI integrated with VS Code's standard settings panel that allows users to enable/disable individual extension features (branch protection, unpushed commit prevention, post-commit notifications, remote sync, submodule management) and configure parameters like protected branch names, polling intervals, and auto-fix behavior. Settings are stored in VS Code's `settings.json` and are scoped to workspace or user level.
Integrates with VS Code's native settings UI rather than requiring a separate configuration file or custom settings panel, providing a familiar configuration experience for VS Code users while allowing per-workspace and per-user setting scopes.
More discoverable than git hooks or config files because it uses VS Code's standard settings UI, and it's more flexible than hard-coded behavior because users can customize features without modifying extension code.
keyboard-shortcut-lifecycle-interception
Medium confidenceHooks into VS Code's keyboard shortcut system to intercept the standard editor close shortcut (`Ctrl+Q` on Windows/Linux, `Cmd+Q` on macOS) and routes it through the extension's `onBeforeShutdown` lifecycle handler. This allows the extension to perform checks (e.g., unpushed commits) and display dialogs before allowing the editor to close, effectively creating a custom shutdown workflow.
Uses VS Code's `onBeforeShutdown` lifecycle hook to inject a blocking check at editor closure time, providing a synchronous safety net that runs before the editor actually closes, though only for keyboard shortcut-based closure.
More reliable than file-watching approaches because it hooks directly into the editor's shutdown lifecycle, but less comprehensive than git hooks because it only works for keyboard shortcut closure and can be bypassed via mouse click.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Git (Submodule) Assistant, ranked by overlap. Discovered automatically through the match graph.
GitDoc
Automatically commit/push/pull changes on save, so you can edit a Git repo like a multi-file, versioned document.
git-mcp-server
An MCP (Model Context Protocol) server enabling LLMs and AI agents to interact with Git repositories. Provides tools for comprehensive Git operations including clone, commit, branch, diff, log, status, push, pull, merge, rebase, worktree, tag management, and more, via the MCP standard. STDIO & HTTP.
Boucle-framework
Autonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.
Verifast AI
Automates code verification with real-time feedback and seamless...
AgentQL
** - Enable AI agents to get structured data from unstructured web with [AgentQL](https://www.agentql.com/).
SonarQube for IDE
Advanced linter to detect & fix coding issues locally in JS/TS, Python, Java, C#, C/C++, Go, PHP. Use with SonarQube (Server, Cloud) for optimal team performance.
Best For
- ✓Teams with strict branch protection policies
- ✓Solo developers working on multiple projects with different branch conventions
- ✓Developers new to a codebase who need guardrails against committing to main branches
- ✓Developers working on shared codebases who need to ensure commits are pushed before machine shutdown
- ✓Teams with CI/CD pipelines that require commits to be pushed to trigger builds
- ✓Developers prone to forgetting to push commits before closing the editor
- ✓Developers working on teams with frequent CI/CD deployments that require commits to be pushed quickly
- ✓Solo developers who want to minimize the gap between local commits and remote backups
Known Limitations
- ⚠Only detects branch switches after they occur — does not prevent the switch, only warns after the fact
- ⚠Requires manual configuration of protected branch names; no automatic detection from GitHub/GitLab branch protection rules
- ⚠Does not integrate with git hooks or server-side branch protection — purely a local warning system
- ⚠CRITICAL: Only works when closing VS Code via keyboard shortcut (`Ctrl+Q` / `Cmd+Q`) — does NOT intercept closure via mouse click on the window close button (X), which bypasses the check entirely
- ⚠Does not detect uncommitted changes (staged/unstaged files) — only detects commits that exist locally but haven't been pushed
- ⚠Requires user to manually push; does not offer automatic push option in the dialog
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
VS Code extension that detects common git (and submodule) issues and helps to solve them
Categories
Alternatives to Git (Submodule) Assistant
Are you the builder of Git (Submodule) Assistant?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →