qe-debug-loop
Debug Loop
Autonomous hypothesis-driven debugging against real data. No guessing, no simulating.
Arguments
<symptom>— Description of the bug or unexpected behavior. If omitted, prompt the user.
Phases
Phase 1 — Reproduce
Run the exact command that shows the bug. Capture and display the REAL output. Confirm the bug is visible.
If the bug cannot be reproduced, stop and explain what was tried.
Phase 2 — Hypothesize and Test (up to 5 iterations)
For each iteration:
- State a specific hypothesis (e.g., "the query targets v2 tables but data is in v3 tables")
- Run a REAL command to test it (e.g.,
sqlite3 [db path] '.tables'thenSELECT COUNT(*) FROM [table])
More from proffesor-for-testing/agentic-qe
code-review-quality
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
1.2Kapi-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
404compatibility-testing
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
381regression-testing
Strategic regression testing with test selection, impact analysis, and continuous regression management. Use when verifying fixes don't break existing functionality, planning regression suites, or optimizing test execution for faster feedback.
213test-automation-strategy
Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.
183technical-writing
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
127