skills.rest
RavBogard
RavBogardCOMMUNITY
Explore all skills by this author →
GitHub

dan:bugsweep

Coordinate auditor agents to detect and fix bugs across a project phase.

Updated Mar 29, 2026
Search Tags:#automation#verification#static-analysis#atomic-commit#auditor#phase-management#bugsweep
One-click install
npx skills add https://github.com/RavBogard/DAN --skill dan-bugsweep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dan:bugsweep
Source: https://github.com/RavBogard/DAN/tree/main/.claude/skills/dan-bugsweep
Command: npx skills add https://github.com/RavBogard/DAN --skill dan-bugsweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn an auditor-driven loop to identify and fix bugs across a project's current phase, reducing manual debugging effort and accelerating delivery.

Core Features & Use Cases

  • Spawns a dan-auditor to perform static analysis, tests, and targeted fixes across all code produced in the phase.
  • Applies fixes with atomic commits and re-verifies after each fix to ensure end-to-end correctness.
  • Enforces a hard cap of three cycles and detects diminishing returns to decide when to escalate.
  • Generates a bugsweep report and captures a fresh VERIFICATION.md per cycle to prevent stale results.
  • Demonstrates two-level orchestration by coordinating dan-verifier and dan-auditor.

Quick Start

Invoke the bugsweep skill on a phase to start a recursive auditor loop that fixes issues until a clean verification passes.

Frequently Asked Questions about dan:bugsweep

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

FAQPage Schema
How do I automate recursive bug fixes and verification across a project phase?▼

Automated bug detection and fixes across a project phase are orchestrated by coordinating auditor agents that perform static analysis and testing, looping through verifications until a clean pass or maximum cycle limit is reached. This recursive process applies atomic commits after each fix.

What is the maximum number of verification cycles allowed for automated bug fixing?▼

The maximum number of verification cycles for automated bug fixing is hard-capped at three. The orchestrator detects diminishing returns within these cycles to decide when to escalate remaining issues instead of continuing to loop.

How does multi-agent orchestration handle issue classification before applying code fixes?▼

Multi-agent orchestration handles issue classification by coordinating verifier and auditor agents to analyze code generation and testing results. Issues are classified before fixes are applied, ensuring atomic commits are only made for targeted corrections.

Does automated phase management generate fresh verification reports after each bug fix?▼

Automated phase management generates a fresh VERIFICATION.md report after each bug fix cycle to prevent stale results. A comprehensive bugsweep report is also produced to document the end-to-end correctness checks across the phase.

When should I escalate unresolved issues instead of continuing the automated bug sweep loop?▼

You should escalate unresolved issues when the automated bug sweep loop detects diminishing returns or hits the hard maximum of three cycles. The system stops looping and escalates if a clean verification pass is not achieved within these constraints.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
novatech2210-cmdnovatech2210-cmd

gsd-audit-milestone

Audit milestone completions against VERIFICATION.md and archiving criteria.

Community
Advanced
RavBogardRavBogard

dan-workflow

Enforce the PLAN to APPLY to UNIFY to SUMMARY loop across DAN workflows.

Community
Advanced
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced