git_submodule_removal

Remove Git submodules atomically by purging configuration and internal storage.

1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/Baneeishaque/ai-suite --skill git-submodule-removal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git_submodule_removal
Source: https://github.com/Baneeishaque/ai-suite/tree/main/.agents/skills/git_submodule_removal
Command: npx skills add https://github.com/Baneeishaque/ai-suite --skill git-submodule-removal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an industrial protocol for the atomic removal of a Git submodule, purging its .gitmodules entry and internal caching directory.

Core Features & Use Cases

  • Unregister and wipe submodule from the working tree and Git config, ensuring no stale references remain.
  • Perform a strict cleanliness audit prior to removal; halt if there are uncommitted changes or unpushed commits unless user confirms override.
  • Purge internal storage at .git/modules/<path> and remove submodule config sections to prevent re-addition conflicts.

Quick Start

Provide the submodule path and invoke the git_submodule_removal skill to perform atomic removal.

Frequently Asked Questions about git_submodule_removal

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

FAQPage Schema
How do I remove a git submodule completely from my repository?

To remove a git submodule completely, you must atomically unregister its path, delete the .gitmodules entry, and purge the internal .git/modules storage to prevent stale references and re-addition conflicts.

What is the best way to delete nested or mismatched git submodule references?

Deleting nested or mismatched git submodule references atomically clears the working tree and Git config sections while purging internal .git/modules storage, ensuring a reproducible state without leftover configuration artifacts.

Can I remove git submodules in CI/CD workflows with uncommitted changes?

You can remove git submodules in CI/CD workflows, but a strict cleanliness audit halts the process if uncommitted changes or unpushed commits exist unless you explicitly confirm an override.

Why does git submodule removal fail when I try to re-add the same path?

Git submodule removal fails on re-addition when internal storage at .git/modules/<path> and submodule config sections are not fully purged, leaving conflicting references that block clean re-registration.

Do I need a traceable commit flow for atomic git submodule removal?

A traceable commit flow is enforced for atomic git submodule removal to align with established git-atomic-commit-construction rules, verifying the working tree and ensuring repository state reproducibility.