github-multi-project

What This Skill Does

The github-multi-project skill is an architectural orchestration tool designed for OpenClaw agents to manage complex software projects. It enables seamless navigation and task distribution across monorepo, polyrepo, and parent-repository project structures. The skill excels at maintaining internal documentation standards, specifically using the .specweave/docs/internal/projects/ path to ensure traceability. By automatically analyzing high-level project tasks, it intelligently segments requirements and distributes them to the correct repository. It acts as the glue for cross-repo work, ensuring that frontend, backend, and shared libraries remain in sync during complex feature rollouts or system migrations.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-github-multi-project

Use Cases

• Monorepo Scaling: Managing workspaces in large projects like Turborepo or Nx where different packages share build logic.
• Polyrepo Coordination: When teams operate on disconnected repositories that require unified specs, such as a frontend application communicating with multiple microservices.
• Parent-Repo Governance: Implementing a central management repository that acts as the single source of truth for architectural specs and task distribution for child implementation repos.
• Feature Flagging across Services: Coordinating a single feature rollout that requires updates to both a database schema in one repo and UI components in another.

Example Prompts

1. "Analyze the current tasks in tasks.md and split them into separate lists for the frontend and backend repositories based on our established multi-project structure."
2. "We are adding a new authentication flow. Create the spec organization structure in .specweave for the shared-auth library and update the distribution mapping."
3. "Check if any pending tasks in the current increment are missing a repository assignment and map them according to the existing service architecture."

Tips & Limitations

• Consistency: Ensure your repository naming conventions in the file system match the project IDs used in the .specweave paths to avoid mapping errors.
• Dependencies: This skill handles task splitting but does not automatically execute cross-repo PRs; always verify the generated task lists before proceeding with implementation.
• Structure: It is recommended to use the 'Parent Repository' pattern for complex setups to maintain centralized control over specs while keeping the codebase modular and decoupled.