{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-ivanhofer-git-assistant","slug":"git-submodule-assistant","name":"Git (Submodule) Assistant","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=ivanhofer.git-assistant","page_url":"https://unfragile.ai/git-submodule-assistant","categories":["code-editors"],"tags":["assistant","git","helper","keybindings","submodule","workflow"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-ivanhofer-git-assistant__cap_0","uri":"capability://safety.moderation.protected.branch.violation.detection","name":"protected-branch-violation-detection","description":"Monitors 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.","intents":["Prevent accidental commits to production branches by getting warned when I switch to a protected branch","Configure which branches should be considered 'protected' for my team's workflow","Quickly switch away from a protected branch via the notification prompt without opening the terminal"],"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"],"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"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Manual configuration of protected branch names in extension settings"],"input_types":["git repository state (current branch name from HEAD)"],"output_types":["VS Code notification toast","Branch switch dialog via notification interaction"],"categories":["safety-moderation","workflow-guardrails"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_1","uri":"capability://safety.moderation.unpushed.commit.prevention.on.editor.close","name":"unpushed-commit-prevention-on-editor-close","description":"Intercepts 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.","intents":["Prevent accidentally closing VS Code and losing work that hasn't been pushed to the remote repository","Get a last-minute reminder to push my commits before shutting down the editor","Decide on-the-fly whether to push or discard unpushed work when closing the editor"],"best_for":["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"],"limitations":["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","Does not work across multiple git repositories in a monorepo — checks only the root repository"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Use of keyboard shortcut to close VS Code (not mouse click closure)"],"input_types":["git repository state (unpushed commits from git log comparison)"],"output_types":["VS Code modal dialog with push/close options","Blocking lifecycle event until user responds"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_2","uri":"capability://automation.workflow.post.commit.push.notification","name":"post-commit-push-notification","description":"Detects 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.","intents":["Get reminded to push my commits immediately after committing so I don't forget","Automatically push commits to the remote repository without manual intervention","Reduce the time between local commit and remote push to minimize work-in-progress exposure"],"best_for":["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","Teams with policies requiring commits to be pushed within a certain timeframe"],"limitations":["Auto-push feature is optional and must be explicitly enabled — default is notification-only mode","Does not validate commit message quality or run pre-push hooks before pushing","Polling-based detection may have slight delay between commit creation and notification (depends on polling interval)","Does not handle push failures gracefully — if push fails, user must manually retry"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Remote repository configured and accessible"],"input_types":["git repository state (new commits detected via git log)"],"output_types":["VS Code notification toast with push action","Optional automatic git push command execution"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_3","uri":"capability://automation.workflow.remote.sync.polling.with.auto.fetch","name":"remote-sync-polling-with-auto-fetch","description":"Runs 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.","intents":["Know when my local branch is behind the remote so I can pull new changes from teammates","Automatically fetch remote changes without manual intervention when my workspace is clean","Get notified of remote updates at regular intervals without constantly checking git status"],"best_for":["Teams with frequent remote commits where developers need to stay synchronized","Developers working on shared branches who want to avoid merge conflicts from stale local branches","Developers who prefer passive notifications over active git status checking"],"limitations":["Polling-based approach means detection is not real-time — relies on configurable interval (specific default interval not documented)","Auto-fetch only runs when workspace has no local changes — conservative approach that may miss updates if user has staged/unstaged changes","Does not automatically pull or merge remote changes — only fetches and notifies, requiring manual pull","Polling adds background CPU/network overhead; interval must be balanced between responsiveness and resource usage","Does not detect rapid remote changes that occur between polling intervals"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Remote repository configured and network accessible","Configurable polling interval setting"],"input_types":["git repository state (local vs remote branch tracking via git fetch)"],"output_types":["VS Code notification toast indicating out-of-sync status","Optional automatic git fetch command execution"],"categories":["automation-workflow","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_4","uri":"capability://automation.workflow.submodule.auto.initialization","name":"submodule-auto-initialization","description":"Detects 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.","intents":["Automatically initialize submodules when I open a project so I don't have to run git submodule commands manually","Ensure submodules are up-to-date with the latest commits from their remote repositories","Reduce onboarding friction for new developers who may not be familiar with git submodule workflows"],"best_for":["Teams using git submodules for dependency management or monorepo structures","Projects with multiple submodules that need to be kept in sync","Developers new to submodule workflows who need automation to reduce manual steps"],"limitations":["Documentation is incomplete — specific submodule detection logic and update strategy not fully detailed","Does not handle nested submodules (submodules within submodules) — support level unknown","Does not validate submodule integrity or detect corrupted submodule state","Auto-update may take significant time for large submodules, potentially blocking workspace initialization","Does not handle submodule branch tracking or custom update strategies"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Repository containing `.gitmodules` file or submodule configuration","Git 2.13+ for reliable submodule support"],"input_types":["git repository configuration (`.gitmodules` file and git config)","submodule remote URLs and commit references"],"output_types":["Initialized submodule directories with checked-out commits","Optional notification indicating submodule initialization status"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_5","uri":"capability://automation.workflow.submodule.auto.update","name":"submodule-auto-update","description":"Monitors 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.","intents":["Keep submodules automatically synchronized with their remote repositories without manual updates","Ensure all team members are using the same submodule commit versions by automating updates","Reduce merge conflicts caused by stale submodule references"],"best_for":["Teams with frequently-updated submodules that need to stay in sync across developers","Monorepo structures where submodule updates are critical to build consistency","Projects where submodule staleness causes integration issues"],"limitations":["Documentation is incomplete — specific update strategy and scheduling logic not fully detailed","Auto-update may cause unexpected changes to submodule commit references, potentially breaking builds if submodule contains breaking changes","Does not validate submodule compatibility or run tests after updating","Aggressive update scheduling may cause frequent workspace disruptions","Does not handle submodule update conflicts or rollback scenarios"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Repository containing submodules","Configurable update interval or trigger strategy"],"input_types":["git submodule state (current vs remote commit references)","workspace change detection (local modifications)"],"output_types":["Updated submodule directories with new commits checked out","Optional notification indicating update status or conflicts"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_6","uri":"capability://automation.workflow.git.state.polling.and.event.integration","name":"git-state-polling-and-event-integration","description":"Implements 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.","intents":["Continuously monitor git state in the background without requiring user interaction","Trigger different extension features (notifications, auto-push, auto-fetch) based on detected git state changes","Ensure git state is checked at critical lifecycle moments (editor open, close, focus change)"],"best_for":["Extensions that need passive git state monitoring without explicit user commands","Teams that want background automation triggered by git state changes","Developers who prefer automatic workflows over manual git operations"],"limitations":["Polling-based approach introduces latency — state changes are not detected in real-time, only at polling intervals","Continuous polling adds background CPU and potentially network overhead (git fetch operations)","Polling interval is a trade-off: shorter intervals increase responsiveness but consume more resources; longer intervals reduce overhead but miss rapid state changes","Does not use git hooks or event-driven mechanisms — relies entirely on periodic state queries","Specific polling interval default value is not documented"],"requires":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Configurable polling interval setting"],"input_types":["git repository state (branch, commits, remote status, submodule configuration)","VS Code lifecycle events (startup, shutdown, focus change)"],"output_types":["Detected state changes that trigger other extension capabilities","Coordination signals between different extension features"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_7","uri":"capability://automation.workflow.configurable.feature.toggles.and.parameters","name":"configurable-feature-toggles-and-parameters","description":"Provides 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.","intents":["Enable only the extension features I need for my workflow, disabling others to reduce overhead","Configure protected branch names, polling intervals, and other parameters without editing config files","Apply different settings per workspace (e.g., stricter settings for production repositories)"],"best_for":["Teams with diverse git workflows who need to customize the extension per project","Developers who want fine-grained control over which automation features run","Organizations with different branch protection policies across repositories"],"limitations":["Specific setting names and configuration options are not documented in available materials","No validation of setting values — invalid configurations may cause silent failures or unexpected behavior","Settings are stored in VS Code's standard settings.json — no custom configuration file format","No UI for managing complex settings like branch name lists — may require manual JSON editing for advanced configurations","Changes to settings require VS Code restart or manual extension reload to take effect (behavior not documented)"],"requires":["VS Code with extension installed","Access to VS Code settings panel (Ctrl+, or Cmd+,)","Basic understanding of VS Code settings UI"],"input_types":["User input via VS Code settings UI","Configuration values stored in settings.json"],"output_types":["Extension behavior modified based on configured settings","Feature toggles enabling/disabling specific capabilities"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-ivanhofer-git-assistant__cap_8","uri":"capability://automation.workflow.keyboard.shortcut.lifecycle.interception","name":"keyboard-shortcut-lifecycle-interception","description":"Hooks 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.","intents":["Intercept editor closure via keyboard shortcut to perform pre-shutdown checks","Display a dialog asking the user to confirm or cancel shutdown based on git state","Prevent accidental editor closure without losing work"],"best_for":["Developers who use keyboard shortcuts to close the editor and want safety checks before shutdown","Teams with policies requiring commits to be pushed before closing the editor"],"limitations":["CRITICAL: Only intercepts keyboard shortcut closure (`Ctrl+Q` / `Cmd+Q`) — does NOT intercept mouse click closure via the window close button (X), which completely bypasses the check","This is a documented limitation and represents a significant gap in coverage","Users can easily circumvent the safety check by clicking the window close button instead of using the keyboard shortcut","Does not work on all operating systems or VS Code configurations (behavior on macOS vs Windows may differ)"],"requires":["VS Code with extension installed","Use of keyboard shortcut to close editor (not mouse click)","VS Code `onBeforeShutdown` lifecycle event support"],"input_types":["Keyboard shortcut event (Ctrl+Q / Cmd+Q)"],"output_types":["Blocking lifecycle event until user responds to dialog","Optional shutdown cancellation or confirmation"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":39,"verified":false,"data_access_risk":"high","permissions":["VS Code with active git repository (`.git` folder in workspace root)","Git extension enabled in VS Code","Manual configuration of protected branch names in extension settings","Use of keyboard shortcut to close VS Code (not mouse click closure)","Remote repository configured and accessible","Remote repository configured and network accessible","Configurable polling interval setting","Repository containing `.gitmodules` file or submodule configuration","Git 2.13+ for reliable submodule support","Repository containing submodules"],"failure_modes":["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","Does not work across multiple git repositories in a monorepo — checks only the root repository","Auto-push feature is optional and must be explicitly enabled — default is notification-only mode","Does not validate commit message quality or run pre-push hooks before pushing","Polling-based detection may have slight delay between commit creation and notification (depends on polling interval)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.51,"quality":0.28,"ecosystem":0.33,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.803Z","last_scraped_at":"2026-05-03T15:20:37.518Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=git-submodule-assistant","compare_url":"https://unfragile.ai/compare?artifact=git-submodule-assistant"}},"signature":"WPL0GAPeF6OXWVWyoBD4e5xXk+6NDLPqBFKyBsTxgYhmmvIj/sYCED/AocoOytJLMVsJlbfGh5mEs70b3u+sBA==","signedAt":"2026-06-20T15:33:45.170Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/git-submodule-assistant","artifact":"https://unfragile.ai/git-submodule-assistant","verify":"https://unfragile.ai/api/v1/verify?slug=git-submodule-assistant","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}