feat(projman): add user-reported issue mode to /debug-report #141

Merged
lmiranda merged 1 commits from feat/issue-139-debug-report-user-mode into development 2026-01-24 17:36:16 +00:00
Owner

Summary

Adds a "user-reported" mode to /debug-report alongside automated diagnostics.

Changes

  • Step 0: Mode selection (automated vs user-reported)
  • Step 0.1: Structured feedback gathering for user-reported issues
    • Plugin/command affected
    • User goal
    • Problem type (error, missing feature, unexpected behavior, docs)
    • Expected vs actual behavior
    • Workarounds
  • Step 5.1: Smart label generation based on problem type
  • Step 6.1: User-friendly issue template with investigation hints
  • Updated Step 7 & 8 to handle both modes

Why

Issue #137 highlighted that the automated diagnostic tests were irrelevant to the actual problem (missing MCP tool schema parameters). Users need a way to report issues they experience, not just test failures.

Test plan

  • Run /debug-report and select "automated" - verify existing behavior unchanged
  • Run /debug-report and select "user-reported" - verify feedback flow works
  • Verify issue is created with correct labels and template

Fixes #139

🤖 Generated with Claude Code

## Summary Adds a "user-reported" mode to `/debug-report` alongside automated diagnostics. ## Changes - **Step 0**: Mode selection (automated vs user-reported) - **Step 0.1**: Structured feedback gathering for user-reported issues - Plugin/command affected - User goal - Problem type (error, missing feature, unexpected behavior, docs) - Expected vs actual behavior - Workarounds - **Step 5.1**: Smart label generation based on problem type - **Step 6.1**: User-friendly issue template with investigation hints - Updated Step 7 & 8 to handle both modes ## Why Issue #137 highlighted that the automated diagnostic tests were irrelevant to the actual problem (missing MCP tool schema parameters). Users need a way to report issues they experience, not just test failures. ## Test plan - [ ] Run `/debug-report` and select "automated" - verify existing behavior unchanged - [ ] Run `/debug-report` and select "user-reported" - verify feedback flow works - [ ] Verify issue is created with correct labels and template Fixes #139 🤖 Generated with [Claude Code](https://claude.com/claude-code)
lmiranda added 1 commit 2026-01-24 17:31:07 +00:00
Adds a new "user-reported" mode alongside the existing automated
diagnostics mode. Users can now choose to:

1. Run automated diagnostics (existing behavior)
2. Report an issue they experienced while using any plugin command

User-reported mode:
- Step 0: Mode selection via AskUserQuestion
- Step 0.1: Structured feedback gathering
  - Which plugin/command was affected
  - What the user was trying to do
  - What went wrong (error, missing feature, unexpected behavior, docs)
  - Expected vs actual behavior
  - Any workarounds found
- Step 5.1: Smart label generation based on problem type
- Step 6.1: User-friendly issue template with investigation hints

This allows capturing UX issues, missing features, and documentation
problems that wouldn't be caught by automated MCP tool tests.

Fixes #139

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda merged commit b39e01efd7 into development 2026-01-24 17:36:16 +00:00
lmiranda deleted branch feat/issue-139-debug-report-user-mode 2026-01-24 17:36:16 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#141