pseudomonorepos

What problem does it solve?

Working across nested parent-child repository trees (pseudomonorepos) often leads to duplicate work, lost context, and irreversible data loss: teams and AI agents recreate specs, blueprints, and code that already exists elsewhere in the tree, and careless repo relocation can wipe out unpushed branches, uncommitted work, and gitignored secrets.

Core Features & Use Cases

• Search-first discipline: Enforces walking up the repo tree to scan all parent and child context-v/ directories for prior work before creating new specs, code, or documentation, with refactor debt logging for skipped searches.
• Safe repo relocation protocol: Mandates a 3-precondition hard stop checklist (synced local branches, catalogued remote branches, backed up secrets) before moving repos within the tree to prevent data loss.
• Cross-tree consistency rules: Provides guidance for aligning branch tiers (development/main/master) across parent and submodule repositories, and patterns for rolling up child changelog and context-v content to parent splash pages.
• Use case: Use this skill when working anywhere in the lossless-monorepo, scaffolding new sub-projects, relocating repos, or building parent sites that aggregate content from child submodules.

Quick Start

Use the pseudomonorepos skill to search all parent and child context-v directories for existing work on your current task before drafting new specs or code, and follow the 3-precondition checklist if you need to move a repo within the tree.