github-sweep-orchestration

Orchestrate multi-agent GitHub repository cleanup with recon, dispatch, and consolidation phases.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Toqsick/MaxClaw --skill github-sweep-orchestration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-sweep-orchestration
Source: https://github.com/Toqsick/MaxClaw/tree/main/.claude/skills/github-sweep-orchestration
Command: npx skills add https://github.com/Toqsick/MaxClaw --skill github-sweep-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires MiniMax-M3, GitHub MCP Server, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of cleaning up GitHub repositories by orchestrating a multi-agent pattern, including Recon, Wave Dispatch, and Consolidation.

Core Features & Use Cases

  • Recon Phase: Inventory and categorize open issues and pull requests.
  • Wave Dispatch Phase: Assign tasks to different types of bees (Closer, Fixer, Feature, Assessment) for parallel processing.
  • Queen Consolidation Phase: Collect results, commit changes, and close issues.
  • Use Case: When a user wants to manage their GitHub repository, clean up open items, or get an overview of open issues and pull requests.

Quick Start

Use the github-sweep-orchestration skill to manage my GitHub repository and clean up all open issues and pull requests.

Frequently Asked Questions about github-sweep-orchestration

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

FAQPage Schema
How do I clean up open GitHub issues and pull requests automatically?▼

Multi-agent orchestration automates GitHub repository cleanup by categorizing open issues and pull requests, dispatching tasks to specialized agents for parallel processing, and consolidating results to commit changes and close resolved items.

What is the multi-agent orchestration pattern for repository cleanup?▼

Multi-agent orchestration for repository cleanup operates in three phases: Recon inventories and categorizes open items, Wave Dispatch assigns tasks to parallel agents, and Queen Consolidation collects results to commit changes and close issues.

Do I need a specific model to run GitHub repository cleanup orchestration?▼

Yes, GitHub repository cleanup orchestration requires configuring the MiniMax-M3 model and the GitHub MCP server to execute multi-agent task dispatch and repository interactions properly.

Can I manage multiple GitHub repository issues in parallel?▼

Yes, you can manage multiple GitHub repository issues in parallel through the Wave Dispatch phase, which assigns categorized tasks to specialized agents like Closer, Fixer, Feature, and Assessment for simultaneous processing.

What's the best way to get an overview of open issues and pull requests?▼

Using the Recon phase of multi-agent orchestration is the best way to get an overview of open items, as it inventories and categorizes all open issues and pull requests in your GitHub repository for downstream processing.

Why does multi-agent orchestration close GitHub issues in batches?▼

Multi-agent orchestration closes GitHub issues in batches because the Queen Consolidation phase collects results from all dispatched agents, commits changes, and closes issues together only after parallel processing is complete.