How do I install the Nested Repo Management skill?

Run npx skillmds@latest add tomevault-io/nested-repo-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nested Repo Management safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nested Repo Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nested Repo Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nested Repo Management?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nested Repo Management by tomevault-io

Name: Nested Repo Management
Author: tomevault-io

Nested Repo Management

Git safety rules for nested repositories in Lupin. Use when committing changes, pushing code, running git commands, managing CoSA submodule, or working with the Firefox plugin or mobile app repositories. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Nested Repository Management

CRITICAL: Lupin contains multiple nested Git repositories that must be managed separately.

Repository Structure

Repository	Location	Remote	Management
Lupin (parent)	`/`	lupin repo	Normal via `/plan-session-end`
CoSA	`/src/cosa/`	`git@github.com:deepily/cosa.git`	Separate context
Firefox Plugin	`/src/lupin-plugin-firefox/`	separate repo	Independent
Mobile App	`/src/lupin-mobile/`	separate repo	Independent

Safety Rules

DO ✅

Stage/commit/push changes in parent Lupin repo
Use /plan-session-end for Lupin commits
Manage nested repos in their own sessions/contexts
Read nested repo's CLAUDE.md when working there

DON'T ❌

NEVER run git commands in nested repo directories from parent context
NEVER commit nested repo changes from Lupin session
NEVER read nested repo history.md from Lupin context
NEVER offer to stage/commit/push CoSA changes when in Lupin

How /plan-session-end Handles This

The workflow automatically:

Detects changes in nested repos
Acknowledges but does NOT commit them
Filters nested paths from git operations
Reminds you to manage them separately

You'll see:

⚠️ Detected changes in nested repositories:
• /src/cosa/ (3 modified files)
• /src/lupin-mobile/ (1 new file)

These are separate Git repositories and will not be included in this commit.
Reminder: Manage nested repositories in their own sessions/contexts.

Detecting Nested Repos

# Find all nested .git directories
find . -name ".git" -type d | grep -v "^./.git$"

Working in Nested Repositories

When working in CoSA (`cd src/cosa/`)

Read /src/cosa/CLAUDE.md for CoSA-specific guidance
Use CoSA's own session management
Commit to CoSA repository separately

When working in Firefox Plugin

Manage as independent project
Has own git history and workflows

When working in Mobile App

Manage as independent project
Has own git history and workflows

History Files to Ignore

From Lupin context, do NOT read:

src/lupin-plugin-firefox/history.md
src/cosa/history.md
src/lupin-mobile/history.md

These are managed by their respective repositories.

Anti-Patterns

Don't git add files in /src/cosa/ from Lupin
Don't try to "fix" untracked files in nested repos
Don't run git status expecting nested repo files
Don't commit "all changes" - check what's actually in Lupin

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: nested-repo-managementdescription: Git safety rules for nested repositories in Lupin. Use when committing changes, pushing code, running git commands, managing CoSA submodule, or working with the Firefox plugin or mobile app repositories. Use when this capability is needed.---# Nested Repository Management**CRITICAL**: Lupin contains multiple nested Git repositories that must be managed separately.## Repository Structure| Repository | Location | Remote | Management ||------------|----------|--------|------------|| **Lupin** (parent) | `/` | lupin repo | Normal via `/plan-session-end` || **CoSA** | `/src/cosa/` | `git@github.com:deepily/cosa.git` | Separate context || **Firefox Plugin** | `/src/lupin-plugin-firefox/` | separate repo | Independent || **Mobile App** | `/src/lupin-mobile/` | separate repo | Independent |## Safety Rules### DO ✅- Stage/commit/push changes in parent Lupin repo- Use `/plan-session-end` for Lupin commits- Manage nested repos in their own sessions/contexts- Read nested repo's CLAUDE.md when working there### DON'T ❌- **NEVER** run git commands in nested repo directories from parent context- **NEVER** commit nested repo changes from Lupin session- **NEVER** read nested repo history.md from Lupin context- **NEVER** offer to stage/commit/push CoSA changes when in Lupin## How /plan-session-end Handles ThisThe workflow automatically:1. Detects changes in nested repos2. Acknowledges but does NOT commit them3. Filters nested paths from git operations4. Reminds you to manage them separately**You'll see**:```⚠️ Detected changes in nested repositories:• /src/cosa/ (3 modified files)• /src/lupin-mobile/ (1 new file)These are separate Git repositories and will not be included in this commit.Reminder: Manage nested repositories in their own sessions/contexts.```## Detecting Nested Repos```bash# Find all nested .git directoriesfind . -name ".git" -type d | grep -v "^./.git$"```## Working in Nested Repositories### When working in CoSA (`cd src/cosa/`)- Read `/src/cosa/CLAUDE.md` for CoSA-specific guidance- Use CoSA's own session management- Commit to CoSA repository separately### When working in Firefox Plugin- Manage as independent project- Has own git history and workflows### When working in Mobile App- Manage as independent project- Has own git history and workflows## History Files to Ignore**From Lupin context, do NOT read**:- `src/lupin-plugin-firefox/history.md`- `src/cosa/history.md`- `src/lupin-mobile/history.md`These are managed by their respective repositories.## Anti-Patterns- **Don't** `git add` files in `/src/cosa/` from Lupin- **Don't** try to "fix" untracked files in nested repos- **Don't** run `git status` expecting nested repo files- **Don't** commit "all changes" - check what's actually in Lupin---> Converted and distributed by [TomeVault](https://tomevault.io/claim/deepily) — claim your Tome and manage your conversions.

Frequently asked questions