audit-sweep-dispatch

Route health-audit findings by severity and effort into parallel agent waves.

2|Updated Apr 8, 2026

Search Tags:#audit #dispatch #triage #code-fix #build-validation #agent-waves

Ready to run

npx skills add https://github.com/DojoGenesis/gateway --skill audit-sweep-dispatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-sweep-dispatch
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/agent-orchestration/skills/audit-sweep-dispatch
Command: npx skills add https://github.com/DojoGenesis/gateway --skill audit-sweep-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It organizes health‑audit results by severity and effort, ensuring that critical (RED) issues are fixed immediately, trivial (YELLOW) tasks are handled in‑thread, and substantial (YELLOW) fixes are delegated to parallel agent waves.

Core Features & Use Cases

Severity‑based routing: Automatically categorizes findings into GREEN, RED, and YELLOW buckets.
Wave planning: Groups substantial YELLOW findings into non‑overlapping agent waves with concurrency limits.
Verification steps: Runs build and test commands to validate each fix before proceeding.
Use case: After running a /health-audit on a large Go codebase, employ this skill to quickly triage results and orchestrate multi‑agent fixes without merge conflicts.

Quick Start

Ask the audit‑sweep‑dispatch skill to triage the latest health audit findings and generate a dispatch plan.

Frequently Asked Questions about audit-sweep-dispatch

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

FAQPage Schema

How do I triage code audit findings by severity and automate the fixes?▼

Triage code audit findings by routing RED, YELLOW, and GREEN results into severity buckets, fixing blocking issues in-thread, and dispatching substantial tasks to parallel agent waves. This workflow verifies builds before launching concurrent fixes.

What is the best way to dispatch multi-agent code fixes without merge conflicts?▼

Dispatch multi-agent code fixes by grouping substantial YELLOW findings into non-overlapping agent waves with concurrency limits. This prevents merge conflicts by ensuring parallel agents work on isolated sections of the codebase.

How do I validate build commands before launching parallel agent waves?▼

Validate build commands before launching parallel agent waves by leveraging file-system tools to run verification steps. The workflow executes provided build and test commands to ensure each fix passes validation before proceeding.

Can I use an automated dispatch workflow for a large Go codebase health audit?▼

You can use this automated dispatch workflow for a large Go codebase health audit by providing a findings array and optional build commands. It organizes health-audit results by severity and effort to orchestrate multi-agent fixes.

When should I handle code fixes in-thread instead of dispatching to agent waves?▼

Handle code fixes in-thread when the audit findings are trivial YELLOW tasks or critical RED blocking issues. Substantial YELLOW fixes should be delegated to parallel agent waves to optimize execution time and resource allocation.