workspace-consolidation

Consolidate fragmented triad workspaces into a single canonical codebase.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Heretek-AI/heretek-skills --skill workspace-consolidation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-consolidation
Source: https://github.com/Heretek-AI/heretek-skills/tree/main/skills/workspace-consolidation
Command: npx skills add https://github.com/Heretek-AI/heretek-skills --skill workspace-consolidation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fragmented triad workflows across multiple repos and divergent git states create sync drift and integration headaches. This Skill consolidates them into a single canonical workspace to ensure consistency across nodes and deployments.

Core Features & Use Cases

  • Detect fragmented workspaces across nodes and identify drift in remotes and branches.
  • Migrate fragmented work to a canonical repository and unify paths, remotes, and branches.
  • Enforce a single, shared workspace path and provide auto-sync hooks to maintain alignment.
  • Support a safe commit-and-push workflow with monitoring and logging to guard against divergence.
  • Offer a migration script and Unity-check tooling to verify consistency across all triad nodes.

Quick Start

Run the migration script to consolidate fragmented workspaces into the canonical openclaw repository.

Frequently Asked Questions about workspace-consolidation

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

FAQPage Schema
How do I consolidate fragmented git workspaces across multiple nodes into one repository?

To consolidate fragmented git workspaces, run the migration script to unify divergent commits, remotes, and branches into a single canonical codebase, preventing sync drift across multi-node deployments.

What causes git repositories to drift apart across different deployment nodes?

Git repositories drift when multi-node deployments use different remotes, divergent commits, or unstandardized local paths. This fragmentation creates integration headaches and inconsistent states across the triad workflow.

What is the best way to automate workspace synchronization after a git migration?

The best way to automate workspace synchronization is by configuring auto-sync hooks and monitoring logging. This enforces a shared canonical path and maintains alignment through a safe commit-and-push workflow.

How do I verify codebase consistency across all triad nodes after path standardization?

Verify codebase consistency across triad nodes by running the Unity-check tooling. This validates that the canonical paths and automated synchronization successfully prevented state divergence.

Does workspace consolidation support recovering fragmented commits from divergent local repos?

Yes, workspace consolidation supports recoverability by migrating fragmented work from divergent local repos into the canonical repository. Migration scripts unify paths and remotes to ensure no commits are lost.