proffesor-for-testing/debug-loop
.claude/skills/debug-loop/SKILL.md
Use when debugging a failing test or runtime error with hypothesis-driven investigation, autonomous command validation, and systematic root cause elimination.
$ install --global
skillsauthnpx skillsauth add proffesor-for-testing/agentic-qe debug-loopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 8:18 PM36.8s1 file scanned
SKILL.md
- name:
- debug-loop
- description:
- Use when debugging a failing test or runtime error with hypothesis-driven investigation, autonomous command validation, and systematic root cause elimination.
- trust_tier:
- 0
- domain:
- debugging
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]) - Record whether the hypothesis was confirmed or rejected
- If rejected, form the next hypothesis based on what you learned
Do NOT make code changes until you have a confirmed root cause.
Important checks:
- Always check both v2 and v3 SQLite tables when data issues are suspected
- Check dependency versions (e.g., sqlite3 vs better-sqlite3)
- Check for hardcoded values that may have been missed
Phase 3 — Fix
Make the minimal targeted fix. Explain:
- What the root cause was
- What you're changing and why
- What the blast radius is (which other code paths are affected)
Before applying, grep for ALL instances of the problematic pattern across the entire codebase.
Phase 4 — Verify
Run the SAME reproduction command from Phase 1. The output must now show correct values. If it doesn't, go back to Phase 2.
Show before/after output comparison.
Phase 5 — Regression
npm test
Run the full test suite. If tests fail, fix them before committing.
Rules
- NEVER guess or simulate output — always run real commands
- NEVER make code changes before confirming root cause
- Always check for the pattern across the entire codebase, not just one file
- If blocked after 5 hypotheses, stop and ask the user for guidance
Related Skills
proffesor-for-testing/qe-xp-practices
development
VerifiedTrustedCommunity
Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.
304SKILL.mdUpdated Apr 11, 2026
proffesor-for-testing/qe-wms-testing-patterns
development
VerifiedTrustedCommunity
Warehouse Management System testing patterns for inventory operations, pick/pack/ship workflows, wave management, EDI X12/EDIFACT compliance, RF/barcode scanning, and WMS-ERP integration. Use when testing WMS platforms (Blue Yonder, Manhattan, SAP EWM).
304SKILL.mdUpdated Apr 11, 2026
proffesor-for-testing/qe-visual-testing-advanced
testing
VerifiedTrustedCommunity
Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.
304SKILL.mdUpdated Apr 11, 2026
proffesor-for-testing/qe-verification-quality
development
VerifiedTrustedCommunity
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
304SKILL.mdUpdated Apr 11, 2026