VSC-MCPServer: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Critical Rules

These rules override all other instructions:

1. NEVER commit directly to main - Always create a feature branch and submit a pull request
2. Conventional commits - Format: type(scope): description
3. GitHub Issues for TODOs - Use gh CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
4. Pull Request titles - Use conventional commit format (same as commits)
5. Branch naming - Use format: type/scope/short-description (e.g., feat/tools/new-tool)
6. Working an issue - Always create a new branch from an updated main branch
7. Check branch status before pushing - Verify the remote tracking branch still exists. If a PR was merged/deleted, create a new branch from main instead
8. Write tests - All new/refactored code requires tests where applicable
9. Run validation before commits - Run npm run build and npm run test and verify no errors before committing
10. No co-authors - Do not add co-author information on commits or pull requests
11. No "generated by" statements - Do not add generated-by statements on pull requests

---

GitHub CLI Commands

gh issue list                    # List open issues
gh issue view <number>           # View details
gh issue create --title "type(scope): description" --body "..."
gh issue close <number>

Conventional Commit Types

Type	Description
feat	New feature
fix	Bug fix
docs	Documentation only
refactor	Code change that neither fixes a bug nor adds a feature
test	Adding or updating tests
chore	Maintenance tasks
perf	Performance improvement
ci	CI/CD changes

VS Code Extension Development Rules

Project Structure:

• Extension source in src/ directory
• Main entry point: src/extension.ts
• Tools in src/tools/
• Server implementation in src/server/
• Tests co-located with source files (*.test.ts)