github-task-splitter

What This Skill Does

The GitHub Task Splitter is a specialized OpenClaw agent designed for complex engineering workflows in multi-repository environments. It acts as an orchestrator that takes a high-level technical requirement or a SpecWeave task and intelligently breaks it down into granular sub-tasks distributed across relevant GitHub repositories. By parsing project architecture and dependency trees, it ensures that your microservices stay synchronized, preventing the common pitfalls of orphaned code changes or disconnected feature releases. It automates the boilerplate of creating cross-repo tracking issues and maps the relationship between parent and child tasks.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-github-task-splitter Ensure you have configured your GitHub authentication tokens within your OpenClaw settings to allow the agent to read repository structures and write issues.

Use Cases

• Microservices Refactoring: When a core API change requires modifications in five different backend services simultaneously.
• Full-stack Feature Rollouts: Coordinating changes between a frontend React repository, a shared UI component library, and a backend node service.
• Cross-Repo Bug Investigation: Tracking a single root cause that manifests as symptoms across multiple linked repositories.
• Dependency Upgrades: Planning a major version update that necessitates changes to sub-modules across an entire organizational ecosystem.

Example Prompts

1. "I need to implement OIDC authentication across our microservices. Please analyze the repository architecture and create tracking issues in the auth-service, gateway, and user-profile repos."
2. "We are migrating to a new API schema. Split the migration task into sub-tasks for all repositories tagged with 'internal-api' and link them all to this primary ticket."
3. "Evaluate the dependencies for our 'dark-mode' feature and generate specific tasks for the frontend-client and shared-design-system repos."

Tips & Limitations

• Tips: Always provide the agent with a clear scope definition. The more descriptive your initial SpecWeave task, the more accurate the distribution of work will be. Use it in conjunction with repository labels to help the agent filter relevant services.
• Limitations: The agent relies on the existing directory structure and repository metadata. It may struggle with highly unconventional or non-standard project architectures where dependencies are not clearly documented in configuration files.