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

Create debugging checklist for marketplace troubleshooting #97

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

Problem

During debugging sessions, issues are misdiagnosed because there's no systematic approach to trace problems through the full plugin loading path.

Proposed Solution

Create docs/DEBUGGING-CHECKLIST.md with systematic investigation steps:

  1. Identify loading path (source vs marketplace vs cache)
  2. Verify files exist at runtime location
  3. Verify venvs exist in INSTALLED location
  4. Verify symlink resolution
  5. Test MCP server startup
  6. Verify fix before committing

Acceptance Criteria

  • Document created
  • Covers all common failure modes
  • Referenced from CLAUDE.md
## Problem During debugging sessions, issues are misdiagnosed because there's no systematic approach to trace problems through the full plugin loading path. ## Proposed Solution Create `docs/DEBUGGING-CHECKLIST.md` with systematic investigation steps: 1. Identify loading path (source vs marketplace vs cache) 2. Verify files exist at runtime location 3. Verify venvs exist in INSTALLED location 4. Verify symlink resolution 5. Test MCP server startup 6. Verify fix before committing ## Acceptance Criteria - [ ] Document created - [ ] Covers all common failure modes - [ ] Referenced from CLAUDE.md
lmiranda commented 2026-01-22 18:31:18 +00:00
Author
Owner
Copy Link

Implementation Complete

Created docs/DEBUGGING-CHECKLIST.md with systematic troubleshooting steps:

Contents

  1. Step 1: Identify the Loading Path - Source vs Installed vs Cache
  2. Step 2: Verify Files Exist at Runtime Location
  3. Step 3: Verify Virtual Environments Exist (most common failure)
  4. Step 4: Verify Symlink Resolution
  5. Step 5: Test MCP Server Startup
  6. Step 6: Verify Configuration Files
  7. Step 7: Verify Hooks Configuration
  8. Quick Diagnostic Commands - One-liner to check all components
  9. Common Issues and Fixes - Table of symptoms → causes → fixes

Also Updated

  • CLAUDE.md - Added Installation Paths section and Debugging section
  • docs/CANONICAL-PATHS.md - Added reference to DEBUGGING-CHECKLIST.md
  • Documentation Index in CLAUDE.md now includes the new file

Acceptance Criteria Status

  • Document created
  • Covers all common failure modes
  • Referenced from CLAUDE.md
## Implementation Complete Created `docs/DEBUGGING-CHECKLIST.md` with systematic troubleshooting steps: ### Contents 1. **Step 1: Identify the Loading Path** - Source vs Installed vs Cache 2. **Step 2: Verify Files Exist at Runtime Location** 3. **Step 3: Verify Virtual Environments Exist** (most common failure) 4. **Step 4: Verify Symlink Resolution** 5. **Step 5: Test MCP Server Startup** 6. **Step 6: Verify Configuration Files** 7. **Step 7: Verify Hooks Configuration** 8. **Quick Diagnostic Commands** - One-liner to check all components 9. **Common Issues and Fixes** - Table of symptoms → causes → fixes ### Also Updated - `CLAUDE.md` - Added Installation Paths section and Debugging section - `docs/CANONICAL-PATHS.md` - Added reference to DEBUGGING-CHECKLIST.md - Documentation Index in CLAUDE.md now includes the new file ### Acceptance Criteria Status - [x] Document created - [x] Covers all common failure modes - [x] Referenced from CLAUDE.md
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#97
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?