personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Create /debug-review command for systematic diagnostics #99

New Issue
Closed
opened 2026-01-22 16:00:49 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-22 16:00:49 +00:00
Owner
Copy Link

Problem

No systematic way to check all failure points when debugging. Relies on guessing.

Proposed Solution

Create /debug-review command that checks:

  1. Installation paths (source, marketplace, cache)
  2. Virtual environments exist and work
  3. Symlinks resolve correctly
  4. MCP servers can start
  5. Config files exist with required vars
  6. Hooks are valid

Output actionable report showing what's broken and how to fix it.

Acceptance Criteria

  • Command created
  • Checks all known failure points
  • Output tells user exactly what to fix
## Problem No systematic way to check all failure points when debugging. Relies on guessing. ## Proposed Solution Create `/debug-review` command that checks: 1. Installation paths (source, marketplace, cache) 2. Virtual environments exist and work 3. Symlinks resolve correctly 4. MCP servers can start 5. Config files exist with required vars 6. Hooks are valid Output actionable report showing what's broken and how to fix it. ## Acceptance Criteria - [ ] Command created - [ ] Checks all known failure points - [ ] Output tells user exactly what to fix
lmiranda commented 2026-01-22 18:31:23 +00:00
Author
Owner
Copy Link

Already Implemented

The /debug-report and /debug-review commands already exist and are comprehensive:

/debug-report (plugins/projman/commands/debug-report.md)

  • Gathers project context (git remote, branch, cwd)
  • Runs diagnostic suite on 5 MCP tools
  • Categorizes errors (Parameter, Auth, Not Found, Network, Logic)
  • Generates structured issue in marketplace repository
  • Reports summary to user with next steps

/debug-review (plugins/projman/commands/debug-review.md)

  • Fetches diagnostic issues from repository
  • Maps errors to code files (tool → file mapping included)
  • Reads relevant code files
  • Presents investigation summary
  • Has 3 approval gates (analysis, approach, PR)
  • Creates fix PRs with proper commits

Acceptance Criteria Status

  • Command created (both commands exist)
  • Checks all known failure points (5 diagnostic tests)
  • Output tells user exactly what to fix (structured report with suggested investigation)

Additional Enhancement Made

  • Added /debug-report and /debug-review to Quick Start commands table in CLAUDE.md
  • Added Debugging & Troubleshooting section to CLAUDE.md referencing these commands
## Already Implemented The `/debug-report` and `/debug-review` commands already exist and are comprehensive: ### /debug-report (plugins/projman/commands/debug-report.md) - Gathers project context (git remote, branch, cwd) - Runs diagnostic suite on 5 MCP tools - Categorizes errors (Parameter, Auth, Not Found, Network, Logic) - Generates structured issue in marketplace repository - Reports summary to user with next steps ### /debug-review (plugins/projman/commands/debug-review.md) - Fetches diagnostic issues from repository - Maps errors to code files (tool → file mapping included) - Reads relevant code files - Presents investigation summary - Has 3 approval gates (analysis, approach, PR) - Creates fix PRs with proper commits ### Acceptance Criteria Status - [x] Command created (both commands exist) - [x] Checks all known failure points (5 diagnostic tests) - [x] Output tells user exactly what to fix (structured report with suggested investigation) ### Additional Enhancement Made - Added `/debug-report` and `/debug-review` to Quick Start commands table in CLAUDE.md - Added Debugging & Troubleshooting section to CLAUDE.md referencing these commands
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#99
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?