- Home
- Skills
- Agents & Orchestration
- dispatch fixes
Works with the AI Agents you already use
dispatch fixes
Coordinate parallel agent workflows to batch, fix, and promote GitHub issues using git worktrees and the gh CLI.
Free
dispatch fixes
Example session with this skill installed
I have 12 open issues with the label 'remediation-v1'. Group them, dispatch agents to fix them in batches of 3, and promote the results to the 'main' branch through 'develop'.
- Read your context and instructions
- Compiled the dispatch fixes
I have analyzed the 12 issues labeled remediation-v1. Based on the commit history, I have confirmed develop is the active working branch and main is the promotion branch. I have batched the issues into 4 groups to minimize merge conflicts.
Dispatch Plan: remediation-v1
| Group | Lead issue | Issues | Branch | Status |
|---|---|---|---|---|
| G-01 | #102 | #102, #105 | bugfix/102-auth-bypass | In progress |
| G-02 | #108 | #108, #109, #112 | tech/108-db-indexing | In progress |
| G-03 | #103 | #103, #104 | bugfix/103-jwt-validation | In progress |
| G-04 | #115 | #115, #116, #120 | bugfix/115-cors-policy | Blocked (G-01) |
Dispatch Logic:
- Groups G-01, G-02, and G-03 have been dispatched to separate git worktrees.
- G-04 is waiting on G-01 due to shared changes in
middleware/auth.py. - All PRs will target
develop. Once verified, they will be promoted tomain.
Next steps
- Review the generated briefs in
docs/remediation/work/dispatch/briefs/. - Monitor the
fix-agentlogs for G-01 through G-03. - Approve the validation report for G-01 to unblock the final batch.
Connects securely to your tools. The creator never sees your data.
About this skill
Remediation at scale often fails when dozens of issues are dumped into a backlog without coordination, leading to merge conflicts and scattered testing. This skill acts as a high-level coordinator that batches issues into logical work units, dispatches coding agents into isolated git worktrees, and gates every single merge and promotion.
What it does
- Issue Batching groups remediation issues by implementation boundary, module, or shared root cause to minimize conflict.
- Parallel Dispatching manages multiple
fix-agentinstances concurrently, each operating in its own git worktree to prevent environment pollution. - Workflow Enforcement identifies the correct working and promotion branches by analyzing PR history rather than trusting outdated documentation.
- Validation Gating performs human-in-the-loop verification for every PR, ensuring migrations, security, and observability criteria are met before merging.
- Progress Tracking maintains a
dispatch.mdstatus table that maps every issue from initial brief to verified promotion.
How it works
- Gather uses the GitHub CLI to pull open issues by source label and analyzes repository conventions to establish the branching strategy.
- Group organizes issues into batches (G-01, G-02, etc.) based on code map impact and dependency order.
- Dispatch initializes subagents or sequential tasks using git worktrees, passing a specific brief to the coding role.
- Integrate validates the resulting PRs against acceptance criteria, handles the merge into the working branch, and promotes the code to the staging/production environment.
Frameworks & tools
Requires Python 3 for internal scripts and the GitHub CLI (gh) for issue and PR management. It relies on git worktree for environment isolation and integrates with codemap.py for impact analysis.
Why this beats prompting it yourself
Manual coordination of multiple agents results in git race conditions and inconsistent PR quality. This skill automates the boring parts of project management—grouping, branch naming, and status tracking—while keeping a human gatekeeper on every high-risk change.
Use cases
- Executing a mass refactor across multiple microservices without manual oversight.
- Patching dozens of security vulnerabilities identified in a design review.
- Managing a "remediation wave" where agents must wait for prerequisite infrastructure PRs to merge.
- Coordinating a team of subagents to resolve a large backlog of technical debt.
Known limitations
Requires an authenticated GitHub CLI environment and support for git worktrees. Parallelism is limited by machine resources and token limits, defaulting to three concurrent agents.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Requires gh CLI and Python 3. Parallel dispatching depends on git worktree support. Does not support automatic merging without human approval.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 12 days ago
- Free with an Agensi account
- Software
Python
Git