debug-workflow

Automated bug investigation orchestrates a structured pipeline coordinating a bug-investigator, bug-fixer, and code-reviewer to diagnose and resolve issues. It performs app-context discovery, interactive user Q&A, diagnosis, code fixes, and automated code review across your codebase.

Coordinating bug fixing and code review agents requires a structured task pipeline that routes a bug report through diagnosis, fixes, and review. The workflow prompts users for context, validates assumptions, extracts test plans, and generates a pull request for final validation.

Yes, automated debug workflows apply across codebases by extracting project context and test infrastructure details. It uses this context to guide tester commands, application logging, and pull request creation, ensuring the fix integrates with your existing software engineering environment.

TDD integrates into automated debug pipelines by extracting test plans from project context during the discovery phase. These test plans guide the bug-fixer in applying test-driven development principles, ensuring code changes are validated against existing test infrastructure before review.

Yes, providing app-context and test infrastructure details is required for bug investigation to function correctly. The workflow extracts these details from your project context to guide tester commands, application logging, and pull request creation throughout the debugging pipeline.

Automated bug fixing requires interactive user Q&A to gather missing application context, validate diagnostic assumptions, and steer workflow decisions. This ensures the bug-investigator accurately diagnoses the root cause before the bug-fixer applies changes and the code-reviewer validates the solution.