skills.rest
lossless-group
lossless-groupOFFICIAL
Explore all skills by this author →
Website𝕏@losslessgroupGitHub

pseudomonorepos

Enforce search-first discipline and safe relocation across nested parent-child repository trees.

4|Updated May 4, 2026
Search Tags:#git-submodules#search-first#pseudomonorepo#context-v#branch-alignment#repo-relocation#changelog-rollup
One-click install
npx skills add https://github.com/lossless-group/lossless-agent-skills --skill pseudomonorepos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pseudomonorepos
Source: https://github.com/lossless-group/lossless-agent-skills/tree/main/pseudomonorepos
Command: npx skills add https://github.com/lossless-group/lossless-agent-skills --skill pseudomonorepos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about pseudomonorepos

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

FAQPage Schema
How do I search for existing specs in nested git submodule trees before writing new code?▼

To search nested git submodule trees, walk up the parent repository tree to scan all parent and child context-v/ directories for existing specs or code before creating new work to prevent duplication and fragmented context.

What is the best way to safely move a git submodule to a new parent directory without losing data?▼

Safely moving a git submodule requires completing a 3-precondition checklist: syncing local branches, cataloguing remote branches, and backing up gitignored secrets to prevent wiping out unpushed work and irreversible data loss.

How do I align branches across parent and child git repositories?▼

Aligning branches across parent and child git repositories requires matching branch tiers like development, main, and master between the parent project and submodules to maintain cross-tree consistency.

Why should I scan parent context directories before scaffolding new sub-projects?▼

Scanning parent context directories before scaffolding sub-projects prevents duplicate work by ensuring existing blueprints and specs in the pseudomonorepo tree are discovered and reused rather than recreated.

How do I roll up child repository changelogs to a parent splash page?▼

Rolling up child repository changelogs to a parent splash page involves aggregating context-v content and changelog entries from nested submodules into the parent repository to maintain unified project documentation.

What happens if I skip searching the repo tree before creating new documentation?▼

Skipping the repo tree search before creating new documentation results in refactor debt logging, as the mandatory search-first discipline enforces scanning parent and child context to avoid fragmented context and duplicate specs.

Related Skills

Explore More Software Engineering Skills→
open-haxopen-hax
6

git-safety-check

Check git branch, working tree, remotes, and submodules before destructive operations.

Official
Intermediate
lossless-grouplossless-group
4

maintain-splash-pages

Scaffold Astro-based GitHub Pages splash pages with Pagefind search.

Official
Advanced
IstoraMandiriIstoraMandiri

submodule-push

Push submodule commits to remote forks and update parent references.

Community
Intermediate
alexknowshtmlalexknowshtml
137

publish-oss

Automate publishing internal monorepo packages as public open source on GitHub and npm.

Community
Advanced