Test Extension
Description
Launch the Extension Development Host to test the VS Code extension in a clean environment.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
Repository README
This is the README for drewipson/claude-code-config, shared by 5 entries
in this directory. It describes the repository, not this entry specifically.
Test Extension
Launch the Extension Development Host to test the VS Code extension in a clean environment.
Instructions
- Ensure clean build state:
# Clean and rebuild
rm -rf dist/
npm run build
**Launch Extension Development Host:**
- Option A: Press
F5in VS Code (recommended) - Option B: Run from Command Palette:
Cmd+Shift+P(Mac) orCtrl+Shift+P(Windows/Linux)- Type "Debug: Start Debugging"
- Select "Run Extension"
- Option A: Press
**What happens:**
- A new VS Code window opens (Extension Development Host)
- The extension is loaded in this window
- Original VS Code window shows Debug Console with extension logs
- Breakpoints in TypeScript code are active
**Testing checklist:**
**Basic Functionality:**
- Extension activates (check Debug Console for "Extension activated")
- Activity bar icon appears (Claude logo)
- Tree views render in sidebar
- No errors in Debug Console
**Memories Tree:**
- Global CLAUDE.md files displayed
- Project CLAUDE.md files displayed
- Markdown sections expandable
- Click to open file works
- Refresh button works
**Commands Tree:**
- Global commands displayed
- Project commands displayed
- Folders expand/collapse
- Create new command works
- Open command file works
**Skills Tree:**
- Skills folders displayed
- SKILL.md files detected
- YAML frontmatter parsed
- Description tooltips show
- Create skill works
**Sub-Agents Tree:**
- Agents displayed with colors
- Color-coded icons render
- Create agent works
- Folders supported
**Hooks Tree:**
- Hooks organized by location/event
- Create hook wizard works
- Edit hook works
- Delete hook works
- Duplicate hook works
**Permissions Tree:**
- Permissions parsed from settings
- Organized by type (allow/ask/deny)
- Click to jump to settings works
**File Operations:**
- Create file with template works
- Rename file works
- Delete file works (with confirmation)
- Move between global/project works
- Copy file path works
- Reveal in Finder/Explorer works
- Create folder works
**Testing file watcher:**
- Manually edit a
.claude/file in terminal - Verify tree view auto-refreshes
- Create new file, confirm it appears
- Delete file, confirm it disappears
- Manually edit a
**Testing cross-platform paths:**
- Verify paths work correctly
- Check file operations don't break
- Test home directory resolution
**Testing error handling:**
- Try to open non-existent file
- Try to create file in invalid location
- Try to parse invalid YAML frontmatter
- Verify error messages are user-friendly
Debugging
Set Breakpoints
- Click in gutter next to line numbers in VS Code
- Red dots indicate activ
Related Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing