research-and-fix

Coordinate parallel sub-agents to diagnose multi-system bugs and generate minimal test-verified patches.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill research-and-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-and-fix
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/research-and-fix
Command: npx skills add https://github.com/dotBeeps/pantry --skill research-and-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep-diagnose elusive bugs by running parallel research agents to uncover root causes across systems, then coordinate a structured opus-based fix.

Core Features & Use Cases

  • Parallel exploratory agents that gather historical context and current state
  • Lateral research and targeted sub-agents to clarify root cause
  • End-to-end fix workflow with tests and minimal code changes

Quick Start

Trigger a multi-phase investigation to identify root cause and implement a coordinated, minimal-fix patch.

Frequently Asked Questions about research-and-fix

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

FAQPage Schema
How do I diagnose hard-to-reproduce bugs when the root cause is unclear across multiple systems?

Multi-system bug diagnosis uses parallel sub-agents to gather historical context and current state across components, synthesizing results to pinpoint root causes. This coordinated approach uncovers elusive issues where prior fixes have failed.

What is the best way to fix bugs that span multiple components and have failed previous patches?

Fixing recurring cross-component bugs requires a phase-based workflow that orchestrates parallel agents to synthesize diagnostic results and implement a minimal final patch verified by tests. This structured approach prevents recurring failures.

Can I use parallel agents to investigate cross-component bugs without prior knowledge of the root cause?

Yes, parallel exploratory agents can investigate cross-component bugs without prior root cause knowledge by gathering historical context and current state simultaneously. Targeted sub-agents then perform lateral research to clarify the underlying cause.

Does automated bug diagnosis provide a verified code patch or just identify the root cause?

Automated bug diagnosis provides both root cause identification and a verified code patch. The workflow synthesizes parallel agent results into a minimal final patch verified by tests, ensuring the fix resolves the diagnosed issue.

When should I use workflow orchestration for bug diagnosis instead of manual debugging?

Use workflow orchestration for bug diagnosis when facing multi-system bugs where the root cause is unclear or prior fixes have failed. It is designed for hard-to-reproduce issues requiring cross-component analysis and historical context gathering.